Grow workflow

Lead Qualification Workflow

Inbound leads decay fast: the ones worth talking to book elsewhere while your team works through a flat queue of everything that filled out the form. This workflow puts a deterministic pipeline between the form and your calendar: every lead gets captured, enriched with what can be known from its email and company, scored by explicit rules, and routed. Hot leads get a booking link immediately; the rest get nurture or a polite pass, and your CRM stays accurate without anyone typing.

Typical timeline

2-4 weeks depending on how many capture points and CRM quirks are involved

Stack

n8n for the pipeline · Postgres for lead state · Cal.com for routing hot leads to a call · Resend for follow-up email · Slack for hot-lead alerts

What we need to start

  • · Your current capture points: forms, inbound email, or both
  • · A working definition of a good lead: who you actually close, in plain language we can turn into rules
  • · CRM access and a booking link (Cal.com or whatever you already use)

How it works

  1. 01

    Capture everything into one pipe

    Form submissions and inbound email land in a single n8n intake with a shared schema, so scoring logic runs once instead of per channel. Deduplication happens here: the same person filling the form twice is one lead, not two CRM records.

    Tools: n8n, Webhooks, Postgres

  2. 02

    Enrich from real signals

    We start with what the lead already gave you: the email domain. A company domain versus a free mailbox provider, a resolvable website, and a role-based address like info@ are all cheap, honest quality signals. Third-party enrichment APIs can layer on top, but the base tier works from data you already have.

  3. 03

    Deterministic scoring

    Scoring is explicit rules, not a model guessing: points for a business domain, for company signals matching your ICP, for message content that describes a real project. Deterministic means you can read the score breakdown for any lead and know exactly why it landed where it did, and tuning is editing rules rather than retraining anything.

    Tools: n8n, Postgres

  4. 04

    Route by score

    Hot leads trigger a Slack alert and an immediate email with a booking link while intent is fresh. Mid-tier leads get a short nurture sequence; low scores get logged and left alone. The routing thresholds are yours to move as you watch what each tier actually converts into.

    Tools: Slack, Cal.com, Resend

  5. 05

    CRM sync and review loop

    Every lead, score, and score breakdown syncs to your CRM automatically, so the pipeline is inspectable rather than a black box. We schedule a review after the first few weeks of real traffic to compare scores against what sales actually experienced and adjust the rules.

    Tools: n8n

You get
  • ✓ The live capture-enrich-score-route pipeline in n8n
  • ✓ A documented scoring rubric your team can read and edit
  • ✓ CRM sync with score and score-breakdown fields
  • ✓ Slack hot-lead alerts and the booking-link email flow
When NOT to use this
  • · You get a handful of leads a month; read them yourself, the context in your head beats any rubric at that volume
  • · You cannot describe what a good lead looks like yet; the rules would encode guesses, close a dozen deals first
  • · Your sales process changes weekly; stabilize who you sell to before automating who you talk to

Frequently asked

Why deterministic scoring instead of AI scoring?

Because you can debug it. When a rule-based score looks wrong, you read the breakdown and edit a rule; when a model score looks wrong, you shrug. AI earns a place for specific judgments, like reading intent in the message body, but the backbone stays rules you own.

What can you really tell from an email address?

More than you would expect: whether the domain belongs to a company or a free mailbox provider, whether that domain resolves to a real website, and whether the address is personal or a role account. None of it is certain on its own, but combined these signals separate serious inquiries from noise reliably enough to route on.

Will good leads get filtered out by mistake?

Some misses are inevitable, which is why nothing is deleted: low scores are logged with their breakdown, not discarded, and a human can skim that tier in minutes. The review loop exists to catch systematic misses and fix the rule that caused them.

Does this work with our existing CRM?

Almost certainly. n8n has native nodes for the major CRMs and can hit any REST API for the rest. The sync writes leads, scores, and breakdowns into fields your team already looks at, rather than adding another tool to check.

Want this running in your business?

We build and run this workflow for clients.

Related services: Custom workflow automation · n8n development agency · Custom automation

Free weekly brief

Steal this workflow

Get new teardowns like this one by email: the steps, the tools, and the honest failure modes. No spam, unsubscribe anytime.