Sales

Only Unsure Leads Wait for a Human: A Self-Hosted n8n Lead Qualifier Scores Each Lead by Confidence and Asks for Approval on Borderline Ones

  • Level Advanced
  • Setup1–3 hrs (estimated)
  • Evidence Some evidence
  • CostNot stated in source
  • No-codeNo
n8nSource-linked

What they did

Inbound leads usually either flood the CRM with spam or get wrongly rejected by rigid filters. This builder's self-hosted n8n workflow cleans each form submission with code, then an AI agent checks the prospect's profile, budget, timeline and scope against their ideal customer rubric and returns a confidence score. High-confidence leads go straight into the CRM and the onboarding email sequence. Borderline or low-confidence leads trigger an approval email, and only approved ones move on; the rest are logged as rejected. A second path reads replies to the email campaign: positive replies alert an admin for a personal close, uninterested ones are archived with no more automatic emails.

How it went

n8n community 'Built with n8n' post by the builder (Oct 31, 2026) with a canvas screenshot: webhook intake, JavaScript normalization, AI agent ICP scoring with structured confidence, high-confidence auto-enroll to CRM and email sequence, borderline leads wait for approval by email, reply sentiment triage, self-hosted n8n in Docker behind Caddy, local models, fallback paths for rate limits. No volume or accuracy numbers given

Worth knowing

  • n8n community 'Built with n8n' post by the builder (Oct 31, 2026) with a canvas screenshot: webhook intake, JavaScript normalization, AI agent ICP scoring with structured confidence, high-confidence auto-enroll to CRM and email sequence, borderline leads wait for approval by email, reply sentiment triage, self-hosted n8n in Docker behind Caddy, local models, fallback paths for rate limits. No volume or accuracy numbers given.

Prompt

Cleaned version rewritten from the source — not a direct quote.

When a new lead comes in from [form], clean up the fields, then score it against my ideal customer rules: [industry, company size, budget, timeline, project scope]. Return a confidence score and a one-line reason. If confidence is above [threshold], add the lead to [CRM] and start [email sequence]. If it's below, email me the lead and your reason with Approve and Reject buttons, and only add it if I approve; otherwise log it as rejected. When a lead replies to the sequence, read the reply: if it's positive, alert me so I can answer personally; if they're not interested, archive them and stop all automatic emails.

Recommended

Try it in Grok Bot

  1. Copy the prompt (button below).
  2. Open Grok Bot chat and paste it. Replace any [bracketed] placeholders.
  3. Connect the listed tools (Email) as connectors when Grok Bot asks.
  4. If the task repeats, ask: "Make this a daily routine."

Alternatives: the same prompt works in n8n, Claude, ChatGPT Agent, OpenClaw.

Set it up

Tools: Email · Stack: n8n

  1. Read the original source for full context.
  2. Connect the tools your agent needs.
  3. Paste the prompt and replace [bracketed] placeholders.
  4. Run once manually and check the output before scheduling it.

Generic suggested steps, not from the source.

Evidence

n8n community 'Built with n8n' post by the builder (Oct 31, 2026) with a canvas screenshot: webhook intake, JavaScript normalization, AI agent ICP scoring with structured confidence, high-confidence auto-enroll to CRM and email sequence, borderline leads wait for approval by email, reply sentiment triage, self-hosted n8n in Docker behind Caddy, local models, fallback paths for rate limits. No volume or accuracy numbers given

Source: Web · 2026-10-31 · Verified by us: not yet · Report broken or outdated

Related use cases

SalesReddit

Prospect B2B leads autonomously for 2 weeks (lessons)

An agent running 24/7 on a Mac Mini finds prospects, verifies emails, sends outreach, makes PDF briefings, and tracks the pipeline, keeping a lessons log so it improves over time.

  • Level Intermediate
  • Setup1–3 hrs*
  • Evidence Strong evidence
OpenClawSource-linked
Inbox & communicationWeb · 2026-10

12 of 20 Prompt Injections Worked on His n8n Email Bot, Then 0 of 60: Let Code Make the Decisions, Not the Model

He built an n8n workflow where a small local model reads customer emails and decides priority, refunds and replies, then attacked it with 20 injection emails, 3 runs each. 12 of 20 worked on the plain version (35 of 60 runs), and the usual 'don't follow instructions in the email' prompt made it slightly worse (13 of 20). Taking every decision away from the model fixed it: the model only fills in a form, and a code step strips hidden HTML, keeps secrets out of the prompt and decides what happens. That got 0 of 60. The cost: only 19 of 36 normal emails were answered automatically, down from 31.

  • Level Advanced
  • Setup1–3 hrs*
  • Evidence Strong evidence
n8nSource-linked
MarketingWeb · 2026-10

118 of 120 AI Social Posts Were Bad and 93 Forgot the Link: An n8n Test, and Why Code Checks Still Missed False Numbers

He built a blog-post-to-5-platforms social workflow in n8n two ways and ran both on 8 posts, 3 times each. The one-prompt version produced 118 bad posts out of 120, and 93 left out the blog link. The version with code-checked rules marked 77 posts ready and sent 43 to a human, and none of the 77 failed an independent checker. But when he read them, 10 of 21 in the first round got the blog post wrong, including saying churn rose from 6.1% to 4.3%. His conclusion: code can check format, not truth.

  • Level Intermediate
  • Setup1–3 hrs*
  • Evidence Strong evidence
n8nSource-linked