How to Build a Lead Routing Workflow

The form worked. The handoff did not. The lead waits in an inbox. Somebody copies it into the CRM later. We build the connection between those steps so an enquiry has a record and a clear next action. The routing rule matters more than the acknowledgement email.

This walkthrough follows the design of our free inbound lead workflow. It uses n8n with HubSpot, Slack and Gmail, plus a connected AI model. It is a starting template to adapt and test, rather than a claim about conversion rates or a ready-to-run production system. If the CRM already handles the flow well, use that feature first.

1. Agree what happens to each enquiry

Write down what makes a lead worth an interruption, what only needs a reply, and what needs a person to read it. Include support requests and job applications. Those are different jobs. A sales score should not decide whether a customer gets help.

Our template keeps its customer profile and score thresholds in one Configuration node. The default hot threshold is 70 and the warm threshold is 40. Those are examples for our offer, not universal sales rules. Change the profile and check the resulting tiers against enquiries your team has already handled.

2. Put different forms into the same shape

The Normalise Lead step maps common field names to one record. A form might send email_address while another sends work_email; both become email. Keep the original message and extra fields. Nothing useful should disappear during the tidy-up.

For a live build, preserve the lead source and submission identifier too. Check required fields before the AI step. An incomplete enquiry should land in a visible review queue, rather than fail quietly because a CRM cannot accept an empty email address.

3. Let AI read, then let visible rules score

The AI model extracts fields such as buying intent, whether a problem is described and whether the message signals urgency. The Score and Decide step does the arithmetic in code. That makes the weights visible and lets the team change a threshold without rewriting a prompt.

Selected weights in the downloadable example

Signal	Points
Matches the customer profile	40
Describes a specific problem	20
Signals a budget	20
Immediate timing	15

The arithmetic is repeatable for the same extracted fields. The model's interpretation can still vary, so test it against real examples and keep unclear cases with a person. A score is a routing aid, not proof that somebody will buy.

4. Save the record before the handoff

The template creates or updates a HubSpot contact by email before routing. Its intended hot branch alerts Slack and sends an acknowledgement; the warm branch replies without the interruption. A no-fit enquiry is recorded rather than deleted. Check that the scored fields remain available after the CRM node, because a node may return the saved contact instead of its input.

Assign an owner and a fallback. An enquiry still needs somewhere to go when that person is unavailable. Protect against sending twice when a form retries. Keep the submission identifier, record the completed actions and make a repeated event safe to process. The starting template needs those rules added for your setup.

An acknowledgement is separate from an ongoing nurture sequence. Your marketer should approve the wording and contact rules before any real sends. Replies, opt-outs and a lead becoming a customer must stop the relevant follow-up, rather than leave somebody in a sequence they have already answered.

5. Run the awkward cases before launch

• Repeat submission: send the same event twice and check that it does not create another lead or send another reply.
• Missing details: an empty email or unclear message reaches review with its original content intact.
• CRM unavailable: the enquiry remains recoverable and an alert reaches the person responsible.
• Different intent: a support request or job application reaches the right person instead of being treated as a lost sale.
• Changed status: a reply or opt-out stops the follow-up actions that should no longer run.

Use test contacts and a test inbox until the branches are checked. Keep real sends off. Your team should be able to explain why each example reached its destination. If the explanation is only that the model thought so, the routing rules need another pass.

Measure what happens after the alert

Record when the enquiry arrives. Track owner assignment and the first useful response. Count enquiries with no owner and failed handoffs as well as successful ones. An instant acknowledgement can hide a lead that waited three days for a person; it is not the same as a faster sales response.

For a different example of preparation with a person at the end, our FRM outreach build researches brands, matches models and drafts the pitch for review. The same boundary belongs here: software carries the information, and the team keeps the relationship.

For the full download set and setup notes, see our free n8n workflow templates. For the wider list of jobs worth doing first, read marketing automations for small teams.