HubSpot + n8n Lead Routing Without Fillout (Full Guide)

If you’ve already read our pieces on Fillout + HubSpot routing and the Fillout vs. Tally vs. Chili Piper comparison, you know Fillout does a clean job. But a lot of the teams I work with at Homegrown Growth Co. are already running n8n as their automation backbone and have no intention of adding another SaaS license just to route a form submission. This tutorial shows you exactly how to replicate that Fillout-based routing workflow using n8n and the HubSpot API directly, with no middleware form tool required.

Why skip Fillout and go native n8n

Fillout is genuinely good at what it does. The friction shows up when your routing logic needs to branch on data you do not have at form-submission time: company size from an enrichment API, rep capacity from a live spreadsheet, territory rules that change quarterly. Fillout’s conditional routing is form-field-based. n8n’s branching is code-level, which means you can enrich first and route second. That single difference changes what the workflow is capable of.

The other factor is cost. Fillout’s paid plans start around $40/month once you need routing and logic features. If your team is self-hosting n8n, that $40 goes to zero. Even on n8n Cloud, you are already paying for the platform and routing is just another workflow. I have migrated three clients off Fillout specifically for this reason, and none of them have looked back. Don’t bolt on a form tool to solve a data problem.

The workflow we are building does five things: receive a form submission via webhook, normalize the payload, optionally enrich the lead, apply routing logic, then create or update a HubSpot contact and assign it to the right owner or sequence. Same outcome Fillout gives you. More control over every step.

// n8n HTTP Request node: check for existing contact
// Method: GET
// URL: https://api.hubapi.com/crm/v3/objects/contacts/search
// Body:
{
  "filterGroups": [
    {
      "filters": [
        {
          "propertyName": "email",
          "operator": "EQ",
          "value": "{{ $json.email }}"
        }
      ]
    }
  ],
  "properties": ["email", "hubspot_owner_id", "hs_object_id"]
}
// If results.total > 0, skip the create
// and only update owner if unassigned

Extend the workflow with enrichment before routing

The reason I push teams toward this architecture over Fillout is that you can slot enrichment into step 3 before any routing decision is made. We have a detailed walkthrough of connecting Clay to n8n for a fully automated enrichment pipeline that pairs well with this workflow. The short version: add an HTTP Request node after normalization that calls your enrichment provider with the email or domain, then route on the enriched fields (employee count, industry, funding stage) instead of whatever the prospect typed into a form field.

Routing on self-reported data is unreliable. People lie on forms, or they just guess. Routing on enriched firmographic data pulled from Clay or Clearbit is not. Those are different categories of signal.

For teams already using HubSpot sequences, this means the right sequence fires automatically based on accurate company data, not a checkbox the prospect selected. I have seen sequence reply rates jump 15 to 20 percent simply because the routing was correct and the messaging matched the actual company profile. That is not a workflow improvement. That is a revenue improvement.

Which approach fits your team

Fillout vs. n8n for HubSpot routing

Choose Fillout if

• Your routing logic is 100% form-field-based and unlikely to need enrichment
• A non-technical team member owns the form and routing rules
• You want a visual form builder and routing UI without writing any code

From $40/mo (routing features) Try Fillout →

Choose n8n if

• You are already running n8n for other automations and want one platform
• You need to route on enriched or external data, not just form fields
• You want to eliminate the Fillout license cost and own the routing logic fully

Free (self-hosted) or from $20/mo cloud Try n8n →

Build it once, own it forever

The Fillout approach gets you to a working routing workflow faster on day one. The n8n approach gets you to a better routing workflow by week two, and it costs you nothing extra if you are already in the ecosystem. Every routing rule lives in a workflow you can version, clone, and extend. When territory rules change mid-quarter (and they always do), you update one Switch node instead of rebuilding a form. For the teams I consult with, that operational ownership matters more than the drag-and-drop UI they are giving up.

If your team is running HubSpot and wants to push further into calendar-based routing, our guide on automating demo scheduling with Cal.com, HubSpot, and n8n extends this exact pattern into the scheduling layer. And if you are evaluating n8n against other automation platforms for your broader stack, review the n8n hub before committing to cloud pricing. The n8n Webhook node docs are also worth bookmarking before you start building.