Skip to main content
Never attach a live trigger to an untested draft. Use the simulator, then publish deliberately.

​
Test Flow

1

Open the simulator

In Flow Builder, click Test Flow (toolbar).
2

Walk the happy path

Confirm copy, personalization, and media for the primary route.
3

Force every branch

Exercise each Quick Reply, Condition outcome, API success, and API failure path.
4

Validate data writes

Check that custom fields and tags update as expected on the test contact.
The in-builder Test Flow simulator validates the graph. A separate Bot Simulator tool may exist for embedding a demo widget on a website — that is for demos, not a substitute for path QA.

​
Publish

  1. Click Publish.
  2. Confirm the Flow shows as published in the Flows list.
  3. Attach or verify triggers (Automation Rules, menus, broadcasts, inbox).
Unpublished edits remain draft-only until you publish again.

​
Safe release practices

Publishing replaces the live graph for contacts already mid-Flow. Breaking structural changes can strand people on missing blocks.

​
After publish checklist

  • Trigger still points at the correct Flow ID/name
  • Default Reply still covers unmatched messages
  • Drip campaigns that reference the Flow still resolve
  • Team knows which version is live

​
Next

Trigger a Flow

Connect rules, inbox, broadcasts, and API.

Manage and duplicate

Copy Flows for safe cutovers.