Sharing a small n8n workflow I built so inbound leads stop slipping through the cracks:
- A Webhook node receives the form/lead payload
- A Code node scores how qualified the lead is (simple, editable rules)
- An IF node branches: qualified leads get appended to a Google Sheets CRM and fire a Slack alert; the rest are logged quietly
- 7 nodes total, tested on n8n v1.58+
It’s free and importable (JSON + a short setup doc), no signup wall: Free sample workflow — Agency Lead Capture · SoloFlows
I’m putting together a few more in the same vein (client onboarding, invoice/payment-status follow-up). Would genuinely value feedback on the scoring logic — and what workflow would actually save you time, since that shapes what I build next.
1 Like
Welcome to the community @anandvc! The webhook-to-scoring-to-Sheets structure is clean for this use case. One concrete improvement for the Code node: output a qualified_reason field alongside the numeric score so the Slack alert tells your team exactly which criteria triggered the flag (e.g., “budget >= 10k AND company_size > 50”). Makes it much easier to spot when the scoring logic needs tuning as you collect more lead data.
Thanks Jay, that’s a really good call. You’re right that a bare number doesn’t tell you much when the alert lands in Slack at 9pm. I went ahead and added a qualified_reason to the Code node, so it now tracks which rules actually fired (business email, has a company, budget over $1k, an actual message instead of one line). The Slack alert shows that as a “Why” line now, so you get something like “business email + budget over $1k” next to the score instead of just the number.
Already pushed it to the free sample. Appreciate you taking the time to suggest it. Anything else you’d want the alert to call out, lead source maybe?