Solution Handbook
A planning guide for the Make lead qualification loop, including the Custom webhook trigger, Run once test path, HTTP module, Make History proof, Jodoo fields, and rollout checklist.
Open handbookMAKE + JODOO
AI Lead Qualification with Make + Jodoo
Use Make with Jodoo to receive inbound lead webhooks, send structured qualification fields through an HTTP module, write scoring fields into Jodoo, and keep sales follow-up trackable.
1
Receive leads through a Make webhook
2
Send structured lead fields through HTTP
3
Write score and tier into Jodoo
4
Keep sales follow-up in one record
5
Review operations, credits, and run status in Make History
VIDEO WALKTHROUGH
What happens in the Make demo
The video shows the Make path: a lead enters a Custom webhook, Make sends structured qualification fields through an HTTP module, and Jodoo keeps the sales record.
A lead enters Make
The scenario starts with a Custom webhook that can receive form, campaign, partner, or internal lead data.
Make sends structured fields
The HTTP module sends score, tier, routing priority, owner, next action, and follow-up context.
History records the execution
The Make History panel confirms the manual run, operation count, credit usage, duration, and data transfer.
Jodoo stores the record
The structured result is written into a Jodoo lead app so the team can filter, assign, and review it.
Sales follow-up stays visible
Hot leads can move into owner queues, alerts, dashboards, and review views from the Jodoo record.
DEMO SUMMARY
Make runs the scenario, Jodoo tracks the lead
This implementation is useful when your team wants a visual Make scenario for lead intake before Jodoo becomes the operational record.
Custom webhook trigger
A lead payload enters Make through a Custom webhook.
HTTP writeback
The Make HTTP module sends structured qualification fields.
History success
Make History shows the manual run completed successfully with two operations.
Scenario usage
The Make run records operation count, credits, duration, and data transfer for the tested lead flow.
Jodoo writeback
Jodoo stores the lead score, tier, source, contact, and follow-up fields.
Reusable loop
Make runs the scenario. Jodoo keeps the sales record.
WORKFLOW KIT
Build the same Make lead loop
Review the handbook, copy the workflow recipe, and use the Jodoo field model when adapting the Make webhook to your own lead sources.
REUSABLE WORKFLOW
The workflow decides. Jodoo keeps work moving.
- 01
Make webhook
Form, campaign, partner source, spreadsheet, or internal system
- 02
Make scenario
Receives the webhook, sends the HTTP writeback, and confirms the run in History
- 03
HTTP module
Sends qualification fields as a JSON post request and parses the response
- 04
Make History
Shows success, operations, credits, duration, and data transfer
- 05
Jodoo writeback
Creates the lead record and returns a data ID
- 06
Sales follow-up
Owner queue, review status, dashboard, and audit trail
WORKFLOW LOOP
From Make webhook to sales follow-up
A lead arrives at a Make Custom webhook from a form, campaign, partner source, or internal system.
Run once puts the Webhooks module into a waiting state so the incoming test payload can be captured.
The Make scenario keeps the event visible as a two-module flow: Webhooks app trigger and HTTP app writeback.
The HTTP module uses a JSON body, post method, parse response, and a saved URL that must be rechecked when temporary endpoints change.
The HTTP request sends score, tier, priority, owner, next action, and follow-up context as JSON.
Make History records the manual run, operation count, credit usage, duration, and data transfer.
The structured result is sent to a Jodoo writeback endpoint or secure middleware layer.
Jodoo creates the lead record and keeps it available for owner queues, review views, dashboards, and audit history.
FIELD MAPPING
Agent output becomes Jodoo fields
| Agent or source data | Jodoo record fields |
|---|---|
| contact_name, company, email, campaign | Contact name, Company, Email, Campaign |
| ai_score, lead_tier, routing_priority | AI score, Lead tier, Routing priority |
| fit_reason, missing_info, next_best_action | Fit reason, Missing information, Next best action |
| follow_up_draft, full workflow output | Follow-up draft, Original agent output |
AGENT RECIPE
Prompt and structured output
Workflow role
Receive an inbound B2B lead payload and return structured fields that Jodoo can store, route, and report on.
Qualification instruction
Score the lead using fit, intent, urgency, completeness, and relevance. Keep the output predictable for the Make HTTP writeback step.
Required output
Return ai_score, lead_tier, fit_reason, missing_info, suggested_owner, next_best_action, follow_up_draft, and routing_priority.
Make module contract
Keep the Webhooks bundle, HTTP method, JSON content type, parse response setting, saved endpoint URL, and Run once validation explicit before handing the workflow to the sales team.
{
"ai_score": 92,
"lead_tier": "Hot",
"routing_priority": "High",
"suggested_owner": "Sales Ops queue",
"next_best_action": "Schedule a discovery call within one business day"
}JODOO STARTER APP
Make lead qualification starter app
Use the field model when configuring a Make Custom webhook and Jodoo writeback workflow.
Included fields
- Record title
- Lead source
- Contact name
- Company
- 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
Suggested views
- Hot leads
- Needs review
- Missing information
- Owner queue
- Make run review
- All qualified leads
Automation rules
- Create or update the Jodoo lead record after the Make HTTP module completes.
- Notify the suggested owner when routing priority is High.
- Move missing-information leads into a review queue.
- Flag records for review when Make History shows a failed HTTP operation.
- Keep the original workflow output in the audit trail.
ROLLOUT CHECKLIST
What to confirm before production
- Choose which lead sources should trigger the Make webhook.
- Agree on scoring thresholds, routing priority, and owner rules.
- Confirm the HTTP module URL is saved before every Run once test.
- Check the endpoint health when using a temporary tunnel.
- Map every Make output field to a Jodoo field.
- Test with synthetic data before production traffic.
- Add error handling and retry alerts before launch.
IMPLEMENTATION REFERENCES
Keep the setup details for your team
Jodoo Starter App Blueprint
The Jodoo field model, recommended views, sample record, and automation rules for adapting the lead app after a Make scenario writes the result.
Open blueprintAgent Prompt + Workflow Recipe
The Make webhook setup, HTTP writeback schema, URL save checks, temporary endpoint health checks, Jodoo writeback notes, and production guidance from the live run.
Open recipeWORKFLOW
From Make webhook to qualified lead record
Make is the orchestration layer here. It catches the lead event and calls the writeback step while Jodoo stores the record that sales can review.
A lead arrives at a Make Custom webhook from a form, campaign, partner source, or internal system.
Run once puts the Webhooks module into a waiting state so the incoming test payload can be captured.
The Make scenario keeps the event visible as a two-module flow: Webhooks app trigger and HTTP app writeback.
The HTTP module uses a JSON body, post method, parse response, and a saved URL that must be rechecked when temporary endpoints change.
The HTTP request sends score, tier, priority, owner, next action, and follow-up context as JSON.
Make History records the manual run, operation count, credit usage, duration, and data transfer.
The structured result is sent to a Jodoo writeback endpoint or secure middleware layer.
Jodoo creates the lead record and keeps it available for owner queues, review views, dashboards, and audit history.
JODOO RECORD
What Jodoo stores
Jodoo keeps the durable lead fields after the Make run: source, contact, company, score, tier, routing priority, owner, and follow-up context.
Record titleLead sourceContact and company detailsAI score and tierFit reason and missing infoSuggested ownerNext best actionFollow-up draftRouting priorityOriginal workflow output
LIVE RUN
A Make scenario wrote the lead into Jodoo
The screenshots use synthetic lead data and show the Make scenario canvas, a successful Make History run, and the Jodoo lead table after writeback.
Make scenario configuration
The Make canvas uses a Custom webhook and an HTTP module to call the Jodoo writeback endpoint.
Successful Make History run
Make History shows the lead scenario completed successfully, including operations, credits, duration, and data transfer.
Jodoo writeback
The Make-qualified lead appeared in Jodoo with score, tier, source, contact, and company fields.
FAQ
Common questions
Answers about using agent platforms with Jodoo records, workflows, and app templates.
Was this Make lead workflow tested end to end?
Yes. A Make scenario History entry shows a successful manual run, and the Jodoo table shows the synthetic lead qualification record created from that run.
Does this require a paid Make plan?
The proof run used a free Make account and synthetic data. Production usage may create costs depending on operation volume, connected services, and endpoint usage.
Can the lead source come from outside Jodoo?
Yes. The source can be any system that can send a webhook payload to Make before the result is written into Jodoo.
Can teams add a model-backed agent step in Make?
Yes. The tested path uses a reliable webhook and HTTP writeback flow. Teams can add a Make AI step or connected model call as long as the output schema remains stable.
What should be checked before running the Make scenario?
Confirm the Custom webhook is waiting for data, the HTTP module URL is saved, the request body is JSON, and the endpoint health check passes if a temporary tunnel is used.
How is this different from a code-first webhook workflow?
Make keeps the lead flow visible as modules on a canvas. Builders can see the Webhooks trigger, HTTP request, operation count, credit usage, and History result before the Jodoo team reviews the record.
What happens if the Make HTTP module fails?
Treat the run as unfinished. Check the saved URL, JSON body, endpoint health, and Make History error before collecting screenshots or using the workflow for real lead traffic.
Can the Make scenario stay inactive during testing?
Yes. For manual validation, Run once can wait for a webhook event without turning on a scheduled or always-on scenario. For production, activate the scenario after endpoint health, quota, retries, and error notifications are ready.
Which Make screens help troubleshoot the lead flow?
Use Scenario Usage, History, module bundle output, HTTP status code, data transfer, operation count, and credit usage to confirm the lead moved through Make before checking the Jodoo record.
Why store the result in Jodoo instead of Make History?
Make History is useful for builders, while Jodoo gives sales teams fields, views, owners, dashboards, workflow status, and audit context.
NEXT STEP
Turn Make lead intake into a reusable sales workflow
Start with this lead qualification loop, then reuse the same Make and Jodoo pattern for support, procurement, project intake, or operations requests.