The 3-node n8n flow that books 12 calls a week
Most lead-gen automations fail for the same reason: they scrape everything and qualify nothing. You end up with 400 "leads" and zero calls. Here is the exact flow I build for clients — and why it stays at three nodes.
When a client asks me to "automate lead-gen," what they actually want is a calendar that fills itself with the right people. Everything else is plumbing. So before touching n8n, I write down the one filter that defines a good lead for them — usually a job title plus a trigger event, like "Head of Growth at a company that just raised a seed round."
That single sentence becomes the scoring prompt in node two. Skip it and you are automating noise. Get it right and the flow does the qualifying a junior SDR would do — except it never sleeps and never forgets to follow up.
The three nodes — and nothing else
1 · Pull — Apollo search → n8n. Pull only titles + the trigger event. Cap it at 50/day.
2 · Score — One AI node. Your "good lead" sentence becomes the prompt. Drop everything below 4.
3 · Push — Survivors go straight to a Cal.com booking link via personalised email.
If the flow needs a fourth node, the problem is your filter — not your automation.
The importable JSON + the exact scoring prompt
This part lives behind your account — not in the email. Log in (or subscribe to Maya's Premium) and it unlocks here and stays unlocked on every device. Forwarding the email won't carry it.