Contact Route
Send each contact down one matching path based on a tag, list, or field value.
What this step does
The Contact Route step sends each contact down one path based on a saved tag, list, or exact contact-field value. Routes are checked from top to bottom, and the first match wins.
Use Contact Route when you have several known values that each need a named path. Use a Conditions step for ranges or more advanced comparisons.
Set up a route
Add Contact Route
Add a Contact Route step where the flow should split.
Choose what to route by
Select Tag, List, or Contact field. Field routes use exact values.
Add and prioritize routes
Add one route for each value. Drag the routes or use the arrow controls to put the highest-priority match first.
Build each path
Add the emails, waits, or actions that should run beneath each route.
Decide what happens without a match
Keep Add an Otherwise path enabled for a fallback. If it is disabled, a contact with no match ends at the Contact Route step.
Test without running the flow
In the Contact Route settings, choose a current contact and select
Test Route. The preview shows the route that would win without running later steps or changing the contact.
If several routes match, the preview explains that the highest route won. Test contacts that cover each named path and the Otherwise path before publishing.
Publishing safeguards
Hiveality checks Contact Route references before publishing. Publishing is blocked when a selected tag, list, company, custom field, or saved field option no longer exists, or when a branch points to a removed step.
Review a route after renaming or deleting one of its source values. If route options temporarily fail to load, use Retry; available built-in fields remain selectable while custom values reload.
Tips
- Put the most specific route first when a contact may match more than one.
- Use the Otherwise path for a safe general follow-up or review queue.
- Use Add step after all branches when every route should return to the same shared sequence.
- Test with a current contact, then use Flow Testing for an end-to-end run before activation.
Related Help Docs
Was this helpful?