Flow Testing
Validate a flow end-to-end before you turn it on.
What this does
This helps you confirm a flow starts, runs each step, and completes as expected before you send real traffic into it.
If you need help selecting a trigger or step, see Flow Triggers and Flow Steps.
Before you start
- Use a single test contact you can edit and reuse.
- Choose a trigger you can fire on demand (form submit or tag added).
Steps
Turn on the flow (or activate it)
Make sure the flow status is active before you test.
Trigger the flow once
Use your test contact to fire the trigger event.
Watch the contact move through steps
If there is a Wait step, confirm it is waiting for something that can become true.
Check for the expected outcome
Verify the email/task/notification ran exactly once.
Verify it worked
- The contact appears in the flow history.
- Each step shows a completion status (or an expected wait state).
- Step badges update as contacts wait, complete, hit an issue, opt out, or interact with email steps.
- The final action ran once with the right content.
Fix attention warnings before publishing
Flow cards and the builder can show Needs attention when a trigger or step is missing required setup. Open the flow and select the flagged node to see what needs to be fixed.
Common warnings include:
- Missing tag or list selections.
- Missing email selection for open or click rules.
- Missing link URL for a specific click rule.
- Missing contact property or comparison value.
- Missing board, booking, store, webhook, wait, or action details.
Publishing is blocked until required warnings are fixed, which helps prevent flows from going live with incomplete trigger or step settings.
Move contacts to a different step (testing aid)
When you need to test a downstream step without re-triggering the full flow, you can move one or more contacts to a different step.
- Open the step contact list in Flow Builder.
- Choose Move contact (single) or Bulk move (multiple).
- Pick a destination step and confirm.
Notes:
- Destination steps must be in the published flow version. If a step exists only in draft, publish first.
- The move preview helps avoid duplicate/no-op moves (for example, when a contact is already at the selected step).
- If you move a contact to a delay step, scheduling is queued automatically.
- If you move a contact to an email step, processing starts immediately after the move.
Troubleshooting
- If the trigger did not fire, confirm the trigger settings match the event.
- If the flow is set to Inactive, trigger events will not start new contacts.
- If the contact is stuck, review any Wait Until steps or conditions.
- If move actions fail, publish the latest draft first and then retry the move.
Related Help Docs
Was this helpful?