Automation Fundamentals
What automation actually is
Automation means having a system execute steps that a person would otherwise perform, triggered by an event or a schedule, with defined inputs and outputs. The core concepts a candidate must hold straight are: trigger (what starts a run), action (what the run does), condition (a decision point that routes the run), variable (a named value carried through the run), and run/execution (one instance of the workflow). Distinguish deterministic steps (same input, same output, every time) from steps that depend on judgment or unstructured input.
Traps to watch for
Questions love to blur three pairs. First, trigger vs. action: a schedule that fires at 9 a.m. is a trigger, not an action, even if it feels like "the thing that happens." Second, condition vs. filter: a filter removes items from a set; a condition branches the flow. Third, idempotency: a well-designed automation can run twice on the same input without duplicating side effects. A question describing "the same record was created twice because the trigger fired again" is testing idempotency, not error handling. Also expect distractors that describe automation as "replacing all human work" - the accurate framing is automating repetitive, rule-based steps while people handle exceptions and judgment.
Rule of thumb
Before automating a task, ask: Is it repetitive, rule-based, and does it have a clear trigger and clear success criteria? If any answer is no, the task is a poor first candidate. Worked example: "Email the team when a form is submitted." Trigger = form submission; action = send email; variable = the submitted name; success criteria = message delivered. That passes all four checks and is a sound automation. "Decide whether a contract is legally risky" fails the rule-based check and should stay human-reviewed.