Create and publish an Automation flow

Create an Automation when a schedule or app event should start a task, such as updating a contact or preparing a broadcast. The trigger starts the flow. Each step performs an action, and a branch chooses the next path based on a condition.

Create the draft

1. Open Automation flows and select Create Automation.
2. Name the flow after the business event and outcome.
3. Choose one trigger and configure its required fields.
4. Add data, connected app, audience, broadcast, routing, or terminal steps.
5. Connect every branch to an intentional next step.
6. Select Save and resolve the issues shown in the editor.

A schedule belongs in the schedule trigger. Do not model long waits between steps. If work must happen at another time, create a separate scheduled flow or schedule a broadcast through the supported step.

When the flow creates a Broadcast, place Select audience earlier on every path. It saves the selected segment version or contact list for that run. Point Schedule a broadcast at that audience step rather than querying recipients again during campaign creation.

Publish, activate, and test

1. Save the draft and resolve the displayed issues.
2. Select Publish to create the version you will run.
3. Check the trigger settings, then select Activate. Activation also enables the configured trigger. Keep unrelated events from reaching the flow while you test.
4. Select Test run, supply controlled input, and inspect the result in run history.

Test runs can send messages or change connected records. Use contacts and records you have permission to test with. Test run uses the active published version. Saving draft changes does not include them in the test. To test changes, deactivate the flow, save and publish the new version, then activate it and select Test run.

Check the input and output of each step. An input is the data a step receives; an output is the result it produces. A successful test of one branch does not prove that every branch works.

Update the published flow

Select Deactivate before publishing changes to an active flow. Edit and save the draft, resolve the displayed issues, then Publish, Activate, and Test run again. Draft edits do not change the previously published version. If a published flow uses a dynamic segment whose rule has since changed, review the update warning and publish the intended revision deliberately. Deactivate the flow before replacing a trigger or action when an incomplete transition could create duplicate work.

Next: Review triggers and steps or monitor runs.