Available nodes
FlowRouter provides purpose-built nodes for every stage of the routing pipeline. Drag them onto the canvas, configure their rules, and connect them to build your routing logic.
Trigger
Every flow starts with a Trigger node. It defines the event that kicks off routing — a form submission, a new contact or deal being created, a property change, or a deal stage transition. Each flow has exactly one trigger, and it determines which object type the flow operates on.
Condition
Condition nodes evaluate a record against one or more rules and split the flow into Yes and No branches. Use any HubSpot property with standard operators — equals, contains, greater than, is known, and more. Combine multiple conditions with AND/OR logic to build precise segments.
Territory
Territory nodes route records based on geographic, industry, or revenue-band rules. Define territories by mapping property values to specific owners or teams. Rules evaluate in priority order, and the record is routed to the first match. No overlap, no ambiguity.
Round Robin
Round Robin nodes distribute records across a pool of reps. Configure weighted distribution so senior reps get more volume, set capacity caps to prevent overload, and enable schedule awareness so leads only route to reps who are currently working. Sticky assignment keeps leads from the same company with the same rep.
Account Match
Account Match nodes check whether an inbound lead belongs to an existing company in your CRM. Matching uses email domain (with exclusions for generic domains like gmail.com), fuzzy company name matching, and custom property rules. Matched records follow one branch; unmatched records follow another — so existing customers always reach their current owner.
Assignment
Assignment nodes set the HubSpot owner field on the record. Assign to a specific user, a team, or dynamically based on the output of an upstream node like a territory match or round-robin result. This is where routing becomes reality — the owner field in HubSpot is updated.
SLA Timer
SLA Timer nodes enforce response-time expectations. Set a time window (e.g., 5 minutes, 1 hour) and define what happens when the clock runs out — reassign the lead, escalate to a manager, or send a notification. SLA timers respect working hours so reps are not penalized for leads that arrive overnight.
AI Classify
AI Classify nodes use an LLM to score and categorize leads based on free-text fields, form responses, or any combination of properties. Use AI classification to prioritize high-intent leads, detect spam, or segment records that do not fit neatly into property-based rules.
Send Email
Send Email nodes fire a notification email when a record reaches a specific point in the flow. Use them to alert assigned reps, notify managers of escalations, or confirm routing actions to the ops team. Emails support dynamic property tokens from the routed record.
Stop
Stop nodes end the flow. Any record that reaches a Stop node is done — no further processing. Use Stop nodes to explicitly terminate branches that should not result in an assignment, like filtered-out spam or records that already have an owner.