When should you use it?
- You use AI to rate inbound leads from a web form
- Your enrichment provider sometimes returns nothing or errors out
- Sales has started to distrust scores that swing for no clear reason
Not for: Auto-rejecting or auto-emailing leads based on the score alone; Scoring on personal traits; keep the rubric to company fit and stated need; Teams with too few leads to justify enrichment costs
What do you need, and what do you get?
You need
- A form webhook and an enrichment service (Apollo, Lusha or similar)
- A written scoring rubric with a fixed scale and labels
- A CRM or base (Airtable, HubSpot) plus a team channel for alerts
You get
- One record per lead, deduplicated by email, always saved
- A score, label and short reason when enrichment succeeded
- A 'not scored' status and reason code (for example enrichment_failed) when it did not
- Team alerts for hot leads and for enrichment failures, kept separate
How does it work, step by step?
- CaptureReceive the form submission by webhook and write the lead to the CRM straight away, matching on email.
- EnrichCall the enrichment service. Route success and failure down two separate branches.
- Score with structureOn success, send the message plus company data to the model with a fixed rubric and a structured output parser.
- Hold back on failureOn failure, skip the model, set status to not scored with a reason code, and alert the team to the enrichment problem.
- Log the contextStore rubric version, model and enrichment timestamp with each score so later changes can be explained.
- Test the bad pathBreak the enrichment credentials on purpose and confirm the lead still saves with no score.
The prompt
Our own prompt, inspired by Yana1 and written to work in n8n, Make and Zapier. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You rate inbound B2B leads using company data and the visitor's message. Rubric version {rubric_version}. Inputs: message: {message}; company data: {enrichment_json}. If the company data is empty, errored or lacks size and industry, return only status not_scored with reason enrichment_failed. Otherwise score 0 to 80 on: fit with {ideal_customer} (0-40), clarity of need (0-20), urgency or timeline (0-20). Then return status scored, score, label (Hot 60+, Warm 35-59, Cold under 35), and a reason under 25 words citing the inputs used. Never judge by personal traits, and never suggest contacting or rejecting the lead.
Inspired by Yana1: Built an n8n Lead Capture Workflow with Apollo, AI Scoring & Failure Handling. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- A model will always return a number if asked. Missing inputs need a hard branch, not a softer prompt.
- Retrying a failed enrichment can create duplicates unless the write is matched on email.
- Keep the lead-saved status separate from the scoring status, or a scoring error can look like a lost lead.
Our take
AI lead scoring has a quiet failure mode: when the inputs are thin, the model still produces a confident-looking number. Yana1 caught this in testing, where the same lead landed anywhere between 25 and 77 once company data was missing, and she responded the right way, by not scoring at all. The record still goes into the base, flagged as not scored, and a separate alert tells the team that enrichment broke. That design choice is worth copying into any intake flow, whether it runs on n8n, Make or Zapier. Replies in the thread add two improvements we built into our version: a reason code next to the missing score, and a record of the rubric version, model and enrichment timestamp behind each score so later changes can be explained. Keep the rubric about the company and the stated need, and do not let the score trigger outreach on its own. In our dry run with three fictional leads (a 40-person logistics firm asking for a quote, a student asking a general question, and a lead whose enrichment call returned an error), the first scored 64 and was labeled hot with a short reason, the second cold, and the third was saved as not scored with enrichment_failed and a team alert, with no number assigned.
Where the time goes back: Reps stop chasing leads with inflated scores or ignoring good ones with deflated scores, and nobody re-checks every score by hand because the unreliable ones never get one.
FAQ
Why not let the model score from the form message alone?
Can I swap Apollo for another provider?
Why is there no original prompt here?
Source and credit
Inspired by Yana1. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Built an n8n Lead Capture Workflow with Apollo, AI Scoring & Failure Handling
- Creator
- Yana1
- Published on
- n8n Community
- Original date
- Oct 23, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- n8n
- AI dry run
- Oct 27, 2026: passed. Dry-run tested by our AI test agent on sample input. Hard branch on missing enrichment; no guessed score; reason codes and rubric logging present.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 27, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.