# AI Lead Qualification with n8n + Jodoo

## Solution handbook

Use this handbook to plan a lead qualification workflow where n8n receives an inbound lead, makes a structured qualification decision, and writes the result into Jodoo for sales follow-up.

## Best fit

- RevOps and Sales Ops teams that want node-level control over lead intake.
- Automation builders who prefer an explicit Webhook -> Agent Decision -> HTTP Request chain.
- Teams that want Jodoo to remain the system of record after an agent workflow runs.

## Problem

Inbound leads often arrive with uneven context. A teammate still has to read the message, infer fit, assign priority, and decide who owns follow-up. n8n can coordinate the decision path, while Jodoo keeps the fields that sales and operations need to review.

## Verified test run

- Platform: n8n Cloud
- Workflow: Webhook -> Agent Decision -> HTTP Request
- Test record: Sophia Reed at Meridian Field Systems
- Jodoo data ID: 6a2005199be799f7b658db80
- Result: the n8n workflow wrote a qualified lead record into Jodoo.

The demo uses an auditable decision node so the workflow can run without external model credentials. In production, teams can replace that node with an n8n AI Agent after connecting their preferred model.

## Jodoo starter app

- App name: AI Lead Qualification
- Form name: Lead Qualification Record
- Public preview: available from the scenario page CTA
- App ID: 6a1f85776c9c72ae9990793f
- Form ID: 6a1f85989cf23588e17c40ba

## Workflow

1. A lead arrives at an n8n Webhook node.
2. The Agent Decision node returns score, tier, fit reason, owner, and next action fields.
3. The HTTP Request node sends those fields to a Jodoo writeback endpoint.
4. Jodoo stores the lead record for owner review, dashboards, and follow-up.
5. Sales teams use Jodoo views to prioritize hot leads and review missing information.

## Jodoo record fields

- Record title
- Lead source
- Contact name
- Company
- Email
- Campaign
- Message or request
- AI score
- Lead tier
- Fit reason
- Missing information
- Suggested owner
- Next best action
- Follow-up draft
- Routing priority
- Review status
- Original agent output

## Rollout checklist

- Confirm which sources can send leads into the n8n webhook.
- Define the scoring rubric with sales and marketing.
- Decide whether the production decision node will use code logic or an n8n AI Agent.
- Keep the output schema predictable before sending data to Jodoo.
- Store Jodoo credentials in n8n credentials or a secure middleware layer.
- Test with synthetic leads before using real customer data.
- Add retry handling, error queues, and review views before production use.

## Success metrics

- Faster first response for high-priority leads.
- Fewer unassigned inbound leads.
- More consistent lead scoring across sources.
- Cleaner handoff between n8n automation, sales operations, and Jodoo records.