How to record an automation’s first run

To record an automation’s first run, show one real test input, capture what triggers the rule, then show the matching run-log entry and its output. An enabled switch alone is not proof of completion.

Open the official Automation First Run visual reference. The sample page describes a 7.35-second still pairing the receipt that triggered the rule with its Finance label. Use the still to plan where the input and result will sit in the frame.

Three shots: input, first run, result

  1. Show the starting input. Pick one real test input approved for recording. Keep a unique, non-sensitive reference for that item and the rule’s starting state visible. Hide any private details before you record.
  2. Capture the first trigger. Enable the rule and submit that input once. Keep the actual wait visible, or label any cut that shortens it.
  3. Verify the result. Find the run-log entry for that same input. Hold long enough for viewers to read the matching reference, the completion status and the expected output.

What if there is no result?

If there is no matching entry, check whether the rule is enabled and the input meets its trigger conditions. If the entry is pending, failed, or missing the expected output, record what you see and do not call the run complete.