Practical guide

Test an automation before activating it

Last materially reviewed 2026-09-20

Quick answerDemonstrate trigger, recipient, action and stop conditions with fictional records before involving customers.
What to know

Setup checklist: write the expected behavior first

Define the trigger, the records it applies to, the intended action and the person responsible for the configuration. Include who must not be contacted and what should happen when the record changes. Capsule documents workflow automation and a testing path, but a available feature is not evidence that your particular configuration is safe. Keep the automation inactive until the expected outcomes are written and demonstrated with fictional records in an authorized evaluation context.

What to know

Test the recipient and boundary

For any message-related action, verify how the recipient is selected and whether the relevant mailbox connection is supported and available. A correct template sent to the wrong person is still a failure. Test a record with multiple contacts, missing information and an unexpected stage change. Do not use real customers as test fixtures. If you cannot establish the actual recipient or stop condition, retain the manual workflow instead of treating activation as the experiment.

What to know

Exercise failure and interruption

Ask what evidence remains if an action does not complete or the result is unclear. Can the team tell whether a message was sent before retrying? Who reviews the exception? Keep original record identity and avoid creating a duplicate merely to retrigger the workflow. A safe recovery path is part of the configuration, not an optional later improvement. Do not assume exactly-once execution or automatic rollback unless the product explicitly supports and demonstrates it.

What to know

Activate narrowly and review

Only after the tests pass should an authorized owner consider a limited live scope. Record what changed and inspect actual outcomes promptly. Keep a supported way to stop further actions without deleting the underlying evidence. If behavior differs from the expected result, pause expansion and reconcile before another attempt. This guide does not activate anything for you; it provides the decision structure for doing so responsibly. Continue to stop rules and failure recovery before relying on the automation for important commitments.

Continue when useful

Next: Define when an automated follow-up must stop

A reply, changed stage or owner decision should trigger a reviewed stop path rather than a blind sequence.

Open Define when an automated follow-up must stop →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Capsule workflow automation — Merchant documentation · capsulecrm.com · Merchant-controlled · checked 2026-09-20