An n8n lead-qualification workflow that hands over useful context.

Start with the questions, not the model.

Write down the minimum details needed to act: what the buyer wants, location or service area, budget range, timing, and a reliable way to reply. Do not ask for information your team will never use. Treat free-text answers as untrusted input and keep sensitive details out of unnecessary tools.

A practical workflow map

1. Capture the event. An n8n Webhook can receive a lead from a form or another service and start the workflow. Validate the source and required fields before doing anything else.
2. Ask for missing context. If key details are absent, send a short follow-up question. Use fixed rules for fields such as budget and location; add Claude only where interpreting a natural-language answer genuinely helps.
3. Record one lead. Find or create the CRM record, store the original enquiry and captured answers, and make duplicate handling explicit.
4. Assign and alert. Route the lead to a named owner with a useful summary, source, timing, and the action required. A human should confirm availability or any promise that depends on live business data.
5. Watch failures. If delivery or CRM update fails, alert a person and preserve enough context to retry safely.

What to measure after launch

Track enquiry-to-first-response time, how many leads arrive with usable context, how many are assigned an owner, and how often the workflow needs manual correction. Establish a baseline before claiming time saved or conversion lift.