Automations

Design a narrow workflow, prove it with safe records, and operate it from durable run evidence.

Expected outcome: Eligible records follow the intended steps, consequential actions remain controlled, and failures are recoverable without duplication.

1. Automate a decision you can already explain
A good automation removes repeatable coordination while preserving ownership, review, and evidence.

2. Write the trigger, exclusions, and expected outcome first
Define the event, eligible records, non-goals, owner, success measure, and safe stop condition before opening the builder.
Review point: Narrow scope is easier to prove and recover

3. Choose the event that should create exactly one run
Check whether updates can retrigger the workflow and whether historical records should be eligible.
Review point: Avoid a trigger that the automation itself recreates

4. Place conditions before consequential actions
Exclude missing consent, wrong workspace, final states, incomplete data, and records already handled by another path.
Review point: Conditions are safety boundaries, not cosmetic filters

5. Make every step explicit and ordered
Use waits deliberately, assign owners, avoid hidden side effects, and place human approval before customer communication or irreversible changes.
Review point: The next person should understand the workflow by reading it

6. Test positive, negative, missing-data, and duplicate cases
Use clearly marked demo records. Confirm both what should happen and what must not happen.
Review point: One successful run is not sufficient validation

7. Review, publish, then turn on intentionally
Confirm the active version, scope, owner, alerting, rollback plan, and expected early volume before activation.
Review point: Publish defines the version; turn on permits execution

8. Monitor run history and pause on patterns
Investigate failures one step at a time. Retry only after checking that a repeated action will not create duplicates or affect customers; restore the previous version when the workflow logic is wrong.

This silent visual walkthrough was screen-recorded from the sanitized Acme Retail demo workspace. Follow the linked written guide for exact prerequisites, role boundaries, edge cases, and recovery.