The routing pipeline
When a trigger fires, FlowRouter executes your flow as a pipeline. The record enters at the Trigger node and moves through each connected node in order — evaluating conditions, matching territories, checking account ownership, and ultimately setting the HubSpot owner field.
The pipeline is deterministic. Given the same record and the same flow, the outcome is always the same. Every decision point is logged, so you can trace exactly why a record was routed to a specific owner.
Entry-once semantics
A record can only enter a flow once. If a contact triggers the flow and is routed successfully, the same contact will not be processed again by the same flow — even if the trigger event fires a second time. This prevents duplicate routing, double-assignment, and the noise that comes with records bouncing through the system repeatedly.
If you need to re-route a record (for example, after a territory change), you can manually re-enqueue it from the FlowRouter dashboard.
Schedule awareness
FlowRouter respects your team's working hours. When a Round Robin node has schedule awareness enabled, it only assigns leads to reps who are currently in their working window. Leads that arrive outside all reps' working hours are held and assigned when the first rep comes online.
SLA Timers also respect working hours. A 30-minute SLA that fires at 5:55 PM does not expire at 6:25 PM if the rep's shift ends at 6:00 PM — the clock pauses outside working hours and resumes when the rep is back.
One active flow per object type
FlowRouter enforces a single active flow per HubSpot object type. You can have one active flow for contacts, one for deals, and one for companies — but not two active flows that both trigger on new contacts. This eliminates race conditions and conflicting assignments.
You can maintain multiple draft flows and swap which one is active at any time. Deactivating one flow and deploying another is instant.