GCGstarcademy
Atomic Knowledge · AutoCAD

Action Recorder

AutoCAD's macro tool that records command sequences for repeatable automation without scripting knowledge.

Definition & Context

Action Recorder captures a sequence of AutoCAD commands, inputs, and coordinate picks, then saves them as an Action Macro (.actm file). You can replay the macro to repeat the same sequence on different geometry — for example, applying a standard annotation set to dozens of drawing sheets, batch-inserting blocks at predefined offsets, or running a consistent cleanup routine (purge + audit + save) across a batch of files.

Unlike AutoLISP or .NET, Action Recorder requires zero programming knowledge. You press Record, perform your workflow normally, then Stop. AutoCAD captures the command names, option keywords, coordinate points, and input values. On playback, you can mark certain inputs as "request user input" — pausing the macro for the operator to pick a point or type a value — making macros semi-interactive.

Limitations include: no conditional logic (if/then), no loops, no error handling. For complex automation, AutoLISP or .NET remains necessary. Action Macros are stored per-user profile unless exported and shared. They also cannot call other macros recursively.

Why It Matters

Action Recorder turns repetitive command sequences into replayable macros without any programming, making it the fastest route to automation for drafters who don't write LISP or .NET — ideal for batch cleanup, standard annotation, and block insertion across many drawings.

Best Practices

  • Insert request-for-input pauses so a macro can pick new geometry on replay.
  • Keep macros short and single-purpose; chain them rather than building one giant recording.
  • Record with absolute vs relative coordinates deliberately depending on reuse.
  • Store .actm files in a shared support path so the whole team can run them.

Common Pitfalls

  • Recording absolute coordinate picks that only work on the original drawing.
  • No input pauses, so the macro blindly repeats on the wrong geometry.
  • System-variable state (osnap, layers) differing at playback time.
  • Over-long recordings that are impossible to debug when one step fails.

Related Concepts

Sources & Further Reading