LeadFlow | Paid Lead Qualification and Follow-up
Self-directed template. Not a deployed client system.

1. Import leadflow-n8n.json in n8n. Keep it inactive during setup.
2. Manual sample -> Sample lead -> Configuration runs without credentials while useAi=false.
3. Test different budget, timeline, service, contact data and consent values in Sample lead.
4. Live AI: choose an OpenAI credential in AI follow-up draft. Set an available model ID and useAi=true in Configuration. AI sends only service/budget/timeline/route context, not email/name. Requests may incur model charges. Model errors stop the branch for review.
5. Webhook: select Header Auth credentials, enable the node and map your form fields. This generic intake is not a Facebook Lead Ads subscription handler. A Meta/Google form connector must deliver normalized fields to it. Configuration deliberately ignores inbound useAi/model overrides.
6. Outputs preserve campaign/source. CRM ready output is a payload, not a CRM write. Human review is pending, not automatically approved. No email, WhatsApp or Slack is sent.
7. Before production: implement durable idempotency, CRM upsert, source authentication, an authenticated review interface, retries and monitoring. Do not attach a sender directly to an unapproved payload.

Input: id, name, email, budget (monthly INR), timeline (days), service, consent (boolean), source, campaign.
Scoring: budget >=50k +40, >=30k +25; timeline <=30 days +35, <=90 +15; supported service +25. Sales threshold 70. Missing fields or absent consent -> hold.

Verification: JSON and embedded JavaScript validated locally. The workflow has not been imported/executed on a live n8n instance.
Documentation: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/ ; https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.if/ ; https://developers.openai.com/api/reference/resources/chat