Testing before you arm it

An automation sends messages to real people from your account. Test it first: the cost of a bad automation is not a bug report, it is a reputation.

Dry run

A dry run walks the automation with a simulated trigger event and shows you what would happen at each step: which branch is taken, what delay applies, what message would be sent, to whom.

Nothing is sent. The run is recorded with a dry_run status so you can see it in the history alongside real runs.

What a dry run proves

• The flow reaches the end rather than dying in a branch.
• The message says what you think it says.
• Conditions and tags behave the way you expected.

What it cannot prove

• That the platform will allow the send. Eligibility depends on the real person, the real conversation and the real timing. See staying inside platform rules.
• That your keyword is a good keyword. Only real comments tell you that.

Broadcasts have their own dry run

A broadcast can be dry-run against its segment to show you how many people it would reach, before it reaches them. For anything going to more than a handful of people, do this every time.

Go live carefully

Arm it on one post, watch the first few runs in the history, then widen. An automation is easy to pause and hard to un-send.