Starting from a template
When you create a new flow, FlowRouter offers pre-built templates for common routing patterns. Each template creates a complete flow with the right nodes and connections already wired up — you just need to configure the specifics (which pool, which territory rules, which Slack channel).
Templates are a starting point, not a constraint. After creating a flow from a template, you can add, remove, or rearrange any node. The template gives you the structure; you fill in the details.
Contact templates
Inbound SaaS
Best for: Inbound growth teams receiving demo requests or trial signups.
The flow starts when a form is submitted. An Account Match node checks if the lead's email domain or company name matches an existing company in your CRM. Matched leads route by territory (so they go to the rep who owns that account's region). Unmatched leads go to a general inbound pool via round-robin. Both paths converge on a catch-all queue as a safety net.
After creating: Connect the Territory Route node to your territories (Team > Territories), and assign a pool to the Inbound Pool node. Configure the fallback queue.
ABM Target Account
Best for: Enterprise ABM teams where known accounts should always go to their dedicated owner.
New contacts are matched against your company database. Confident matches route to the account owner — the rep already assigned to that company in HubSpot. Everything else (possible matches and unknowns) goes to a new business queue for manual review.
After creating: Review the confidence threshold on the Account Match node. The default (75%) works for most teams. Lower it if you want more aggressive matching.
Speed to Lead
Best for: High-velocity inbound teams where response time is critical.
Form submissions are immediately round-robined to your inbound pool. A 5-minute SLA starts counting. If the assigned rep doesn't engage the lead within 5 minutes, the flow escalates to a manager. Simple and opinionated — no matching, no territory logic, just fast assignment with accountability.
After creating: Assign your inbound pool to the Route node. Set the escalation target on the Fallback node (a specific manager or a secondary pool).
Partner Sourced
Best for: Partner and channel teams routing referral leads.
Triggers when a contact's lead source is set to "partner." Leads are round-robined across your partner AE pool. A Slack notification fires so the channel team knows a new referral came in. If the pool is empty (all reps unavailable), the lead falls through to a partner ops queue.
After creating: Create a "Partner AEs" pool under Team > Pools and assign it to the Route node. Connect the Slack notification to your partner channel.
Deal templates
Deal Stage Handoff
Best for: SDR-to-AE handoffs when a deal reaches a qualifying stage.
Triggers when a deal's stage changes. Routes the deal by territory — matching the associated company's geography or segment to the right AE team. Falls back to a sales manager if no territory matches.
After creating: Set up territories under Team > Territories with your AE assignments. The trigger will fire on any stage change — you may want to add a Condition node to filter for a specific stage (e.g., "Qualified").
Deal Size Routing
Best for: Teams that split deals between enterprise and mid-market reps based on deal value.
New deals are checked against a dollar threshold (default: $50,000). Deals above the threshold route to an enterprise AE pool. Deals below go to a standard pool. Both paths fall through to a sales ops queue if the pools are empty.
After creating: Adjust the amount threshold in the Condition node. Assign your enterprise and standard pools to the two Route nodes.
Win-Back / Renewal
Best for: Customer success and retention teams managing closed-lost reactivation or upcoming renewals.
Triggers when a deal's stage changes (typically to a renewal or re-engagement stage). Routes to a CSM pool via round-robin with a 24-hour SLA. If the CSM doesn't engage within 24 hours, escalates to a CS manager.
After creating: Assign your CSM pool to the Route node. Add a Condition node before the Route if you want to filter for specific deal stages. Set the escalation target on the Fallback node.
Company templates
Named Account Assignment
Best for: ABM and enterprise sales teams who treat target accounts as a distinct tier with dedicated AE coverage.
Triggers when a new company is created. A Condition node checks the is_target_account property — companies flagged as target accounts route by territory to the AE who owns that region, while everything else falls through to an unassigned queue. The territory route also falls back to the queue if no territory rule matches.
After creating: Set the is_target_account field name to match the boolean property your team uses to flag strategic accounts, and assign your territories (Team > Territories) to the Territory Route node.
Account Re-routing
Best for: Teams managing territory or segment changes without rebuilding routing logic — when a company's size, segment, or region property shifts, ownership shifts with it.
Triggers when the numberofemployees property changes. A Condition node splits the flow at a 200-employee threshold: enterprise-sized accounts route through a territory rule, and smaller accounts go to an SMB round-robin pool. Both paths fall back to an ops review queue if the assignment can't be made.
After creating: Adjust the headcount threshold in the Condition node to match your segment definition, then wire the Enterprise Territory Route to your territories and the SMB Pool to your round-robin pool.
Bulk Import Assignment
Best for: Outbound teams importing target account lists from Apollo, LinkedIn Sales Navigator, or similar tools who need owners assigned the moment a company lands in HubSpot.
Triggers when a new company is created. The flow immediately round-robins the company across an AE pool, fires a Slack notification so the team knows a new account is ready to work, and falls back to an unassigned queue if the pool is empty.
After creating: Assign your AE pool to the Route node, connect the Slack notification to the channel your AEs watch, and configure the fallback queue so imports never silently disappear.
Rep Departure Redistribution
Best for: RevOps teams managing rep offboarding who need company ownership to redistribute automatically instead of running a one-off manual reassignment job.
Triggers when the hubspot_owner_id property changes. A Condition node checks whether the new owner matches a departing rep's ID — if yes, the company is round-robined across the remaining AE pool; if no, a Stop node ends the flow without reassignment so companies owned by other reps are left alone. The active branch falls back to a sales manager if the pool is empty.
After creating: Replace the placeholder value in the Condition node with the departing rep's HubSpot owner ID, assign the remaining AE pool to the Route node, and set the sales manager as the fallback rep.
Customizing after creation
Every template is fully editable once created. Common modifications:
- Add a Condition node to filter by lifecycle stage, lead source, or any HubSpot property before routing
- Add an SLA node after the Route to enforce response time expectations
- Add a Send Email or Slack notification to alert reps or managers when leads are assigned
- Add a Sequence Enrollment node to automatically start outreach after routing (requires Sales Hub Professional)
- Swap round-robin for territory routing (or vice versa) by changing the Route node's mode
- Add a second fallback for multi-tier escalation