What should the agent actually decide?

A useful first version answers a narrow operational question: should this inbound lead go to sales now, enter a nurture queue, or receive a request for missing information? It does not decide whether a person is worthy of attention. The route must follow published business criteria such as company type, problem fit, buying timeframe and requested product.

Keep three kinds of information separate: what the lead submitted, what your systems verified, and what the model inferred. A model may summarise intent from free text, but an inference cannot silently become a CRM fact.

What does the n8n workflow look like?

Text equivalent: the workflow validates an inbound record, retrieves existing CRM context, extracts structured evidence, calculates a route with versioned rules and sends exceptions to a person. Only then may it update the correct record or prepare a follow-up draft.

Build the AI lead qualification agent step by step

1. Define one decision and three routes. Start with sales review, nurture and missing information. Give every route an owner and response-time target.
2. Create a versioned scorecard. List allowed evidence, weights, thresholds and disqualifying conditions. Store the scorecard version with every result so future audits can reproduce the decision.
3. Normalize inbound data. Create stable fields such as lead_id, source, message, company, consent_state and received_at. Reject malformed or unauthorised input before a model call.
4. Retrieve existing CRM context. Search by verified identifiers, not a fuzzy name alone. If several records could match, stop and ask a person. Preserve the current owner and open opportunity.
5. Extract evidence with AI. Ask for a fixed schema containing use case, explicit timeframe, requested outcome, quoted evidence, missing fields and confidence. Tell the model to return unknown rather than complete absent facts.
6. Calculate the route outside the model. Use IF, Switch or code to apply your scorecard. Validate enums, evidence fields and source IDs. Never accept a free-form “hot lead” label as the final decision.
7. Add approval and idempotent writes. Send uncertain, strategic and policy-exception cases to a salesperson. Bind approval to the exact proposed CRM update and use the lead ID as an idempotency key.
8. Test and monitor. Run a dated dataset of good fits, poor fits, sparse enquiries, duplicate contacts, injection attempts and edge cases. Review outcomes by source and scorecard version.

Use a structured result, not a persuasive paragraph

{
  "lead_id": "lead_2048",
  "fit_signals": ["requested workflow automation", "team of 12"],
  "intent": "evaluating_training",
  "timeframe": "unknown",
  "missing_fields": ["decision_timeline"],
  "recommended_route": "request_information",
  "scorecard_version": "2026-10-05",
  "source_ids": ["form_781", "contact_992"],
  "needs_human_review": true
}

The workflow should calculate recommended_route again from the validated fields. That catches prompt drift, malformed output and a model result that contradicts your business rules.

Permissions and privacy

• Give the agent read access only to the CRM fields required for qualification.
• Do not put entire email histories or private notes into the prompt by default.
• Exclude sensitive and protected attributes from the scorecard, including model-inferred proxies.
• Keep marketing consent, service enquiries and legitimate-interest decisions distinct.
• Require approval before sending claims, discounts or promises on behalf of sales.
• Log source IDs, scorecard version, reviewer and final write result without copying unnecessary personal data.

For organisations operating under GDPR, purpose limitation, data minimisation, accuracy and transparency need to be designed into the workflow. This article is a technical pattern, not legal advice.

Failure paths and test matrix

Success criteria

• Every route can be reproduced from verified fields and a named scorecard version.
• Missing facts remain unknown instead of becoming confident guesses.
• Duplicate and currently owned records are preserved.
• No CRM write or outbound message occurs outside the approved branch.
• Salespeople can override a route with a recorded reason.
• False accepts and false rejects are reviewed separately, not hidden in one accuracy number.