Enrich and Route Inbound Leads Automatically

Capture and pass the form submission instantly

Wire your form (a HubSpot form, a website form, Typeform, whatever you use) to fire a webhook on submission into your orchestrator (n8n or Zapier) or directly into a Clay table. Instant is the whole idea: begin enrichment the moment someone hits submit, not on an overnight batch, because the intent you are racing against decays in minutes. In n8n, a Webhook trigger node receives the submission; in Zapier, a form-app trigger or a Webhooks-by-Zapier catch hook does the same.

Capture whatever the form has plus the email, and any enrichment hints like a company field. Even a bare email is enough to proceed, because enrichment fills in the rest from the domain. Do not gate the pipeline on a rich form; long forms suppress conversion and the enrichment makes them unnecessary.

Capture the page they submitted from and any UTM or campaign parameters too. The source page ('/pricing' versus '/blog') and the campaign meaningfully improve both routing and the context you hand the rep, and they are free to grab at submission time but impossible to reconstruct later.

Enrich the lead in Clay

Send the lead into a Clay table that auto-enriches each new row: resolve the company from the email domain, pull company size and industry, identify the person's role and seniority, fetch tech stack if it is relevant to fit, and, critically, check whether the company or contact already exists in your CRM to catch existing customers and open opportunities. All of this runs in seconds per row, which is what makes second-level speed-to-lead achievable instead of aspirational.

Flag personal-email domains (gmail, outlook, yahoo, and so on) in their own column, because they are both harder to enrich, since there is no company domain to resolve, and often lower B2B intent. You do not necessarily discard them, but routing should treat a personal email differently from a corporate one rather than failing silently on it.

Use Clay's waterfall pattern for the enrichments that miss often, stacking two or three providers so a gap in one falls through to the next. Inbound leads are higher-value than cold lists, so the enrichment coverage matters more here; a lead that fails to enrich should route to a human fallback, not get auto-classified as nurture on missing data.

• Company resolved from the email domain
• Company size and industry
• Person role and seniority
• Existing CRM record / open-deal check (the most important field)
• Tech stack, if relevant to fit
• Personal-vs-corporate email-domain flag

Score the lead against your ICP

Add a Clay AI column that scores the enriched lead against your ICP and assigns a routing tier. Reuse the rubric from your account-scoring workflow so a sourced account and an inbound lead are judged by the same standard, which keeps your whole funnel coherent. The output should be a simple, machine-actionable tier plus a one-line reason, because the orchestrator branches on the tier and the rep reads the reason.

Keep the scoring fast and rule-friendly: hot, warm, or nurture, with a clear reason and an explicit existing-customer flag. This is a routing decision made in seconds, not a deep account analysis, so the prompt should be lean and decisive rather than nuanced and slow.

Handle the existing-customer case inside the scoring output explicitly. If the CRM match shows a current customer or an open deal, the score should say so and direct the lead to the account owner, never to a new-business rep, because cold-pitching a customer is the single most embarrassing routing failure.

Score this inbound lead for routing. Use ONLY the enriched data.

Lead: /Full Name, /Title at /Company
Company size: /Employees, Industry: /Industry
Email type: /Email Domain Type (work/personal)
Existing CRM record: /CRM Match
Source page / message: /Source Page, /Message

Return JSON only:
{"tier": "hot|warm|nurture", "reason": "<one sentence>", "is_existing": true|false}

Rules:
- If CRM match shows an existing customer or open deal: set is_existing true, and reason must say to route to the account owner (NOT new business).
- tier 'hot' if: ICP fit (industry in {{ICP}}, size in {{RANGE}}, decision-maker title) AND a work email AND a buying-intent signal (demo request, pricing page, 'pricing'/'demo' in message).
- tier 'nurture' if: clearly non-ICP, a student or job seeker, or a competitor.
- otherwise: tier 'warm'.

Build the routing rules in n8n/Zapier

In your orchestrator, branch on the tier and the other attributes. Route hot leads to the correct rep using your real assignment logic: round-robin within a territory, by company-size segment, or to the existing account owner when it is a current customer or open deal. Route warm leads into a lighter sequence and nurture leads into marketing automation. The orchestrator is where your go-to-market routing policy stops being a wiki page and becomes executable code that runs identically every time.

Handle the existing-customer case as an explicit, early branch: if is_existing is true, route to the account owner or CS and stop, never falling through to a new-business assignment. This single branch prevents the most damaging routing error there is, and it belongs near the top of your logic so it cannot be skipped.

Build a fallback owner for any lead that fails the routing rules, the personal-email leads that could not be enriched, the edge cases, the weird ones. A real human owns the fallback bucket and works it, so that a lead which matches no rule lands on someone's desk rather than disappearing into a gap in the logic.

Assign in the CRM and alert the rep instantly

Have the workflow create or update the lead in HubSpot or Salesforce with all the enriched fields, the score, the tier, and the reason, then set the owner per the routing rules. Immediately post a Slack message to the assigned rep with the key context and a direct link to the record. The whole sequence from submission to rep alert should complete in well under a minute; that speed is the entire value proposition, so measure it and protect it.

Make the Slack alert genuinely actionable: who they are, where they work, the source page and intent, the tier and reason, and one-click links to the CRM record and their LinkedIn. The Slack alert with context is what actually drives fast action; an assignment buried in the CRM gets noticed hours later when the rep next happens to check, by which point speed-to-lead is already lost.

Start the speed-to-lead clock on assignment and surface it. A rep who sees 'this lead came in 90 seconds ago, reach out now' behaves differently than one who has no idea how fresh the lead is.

Monitor speed-to-lead and tune

Track two things: time-from-submission-to-first-touch, and routing accuracy. If reps report mis-routed leads or low-quality 'hot' leads, tighten the scoring rubric, because a hot tier that is often wrong trains reps to ignore the tier entirely. If enrichment is missing data for a meaningful share of leads, add a fallback provider in Clay's waterfall or send the misses to the human fallback owner rather than letting thin data drive a bad auto-classification.

Watch your enrichment credit usage at volume. Cache or skip enrichment for already-known domains, and avoid re-enriching the same company on every form fill from it. Inbound volume can spike unpredictably, and an unbounded per-lead enrichment cost is a budget surprise waiting to happen.

Periodically audit the nurture bucket for false negatives, the real buyer who got mis-scored as nurture and quietly buried. The cost of a mis-scored nurture lead is invisible (you never hear about the deal you didn't get), so you have to go looking for it deliberately. Once tuned, the pipeline runs itself and you have both faster speed-to-lead and reps focused only on qualified inbound.