Solution Handbook
A planning guide for the Make vendor intake loop, including Custom webhook setup, Run once validation, HTTP module mapping, Jodoo fields, and rollout notes.
Open handbookMAKE + JODOO
AI Vendor Intake Review with Make + Jodoo
Use Make with Jodoo when procurement wants a visible Custom webhook, Run once bundle, HTTP module mapping, and scenario history before Jodoo stores the vendor review record.
Capture supplier intake through a Make Custom webhookInspect the incoming bundle and mapped HTTP body during Run onceWrite vendor risk and document follow-up fields into JodooUse Make history to review operations, timing, and writeback response
VIDEO WALKTHROUGH
What happens in the Make demo
The video shows Make reviewing a synthetic vendor intake request, sending structured review fields, and Jodoo storing the procurement record.
Make waits for a vendor bundle
The proof uses a Custom webhook in Run once mode so the incoming supplier payload is visible on the scenario canvas.
The HTTP module maps the review fields
The module sends vendor name, missing documents, risk, recommendation, reviewer, and status as a JSON request.
Run history shows the writeback response
Make confirms the HTTP module completed and returned a Jodoo data ID from the bridge.
Jodoo keeps the vendor review record
Procurement can review document completeness, medium-risk suppliers, conditional approvals, and owner queues in Jodoo.
DEMO SUMMARY
Make reviews the vendor, Jodoo tracks follow-up
This implementation is useful when teams want visual scenario orchestration before Jodoo becomes the shared vendor review record.
Visual scenario
Make shows the vendor intake flow as a webhook module connected to an HTTP writeback module.
Run once capture
The scenario waits for the test request and records the incoming vendor bundle.
Mapped HTTP request
The HTTP module sends the supplier review fields as a JSON body to the Jodoo bridge.
History response
Make records status, operations, duration, and the Jodoo data ID response.
Jodoo follow-up
The Jodoo record keeps document status, risk, recommendation, owner, and review notes.
Scenario recipe
The recipe focuses on webhook URL checks, saved HTTP module fields, and run-history validation.
PLATFORM SETUP NOTES
What is specific to Make
The Jodoo record model can stay consistent, but each agent platform has a different build style, testing view, and production handoff.
Run once visibility
Make is useful when stakeholders want to see the incoming vendor bundle and module response during the first proof run.
HTTP save check
After changing the bridge URL or JSON body, reopen the HTTP module and confirm the saved values before sending test data.
History review
Use scenario history to review module success, operations, credits, duration, and the returned Jodoo data ID.
Production routing
Routers, error handlers, and notifications should be added after the procurement field model is approved.
WORKFLOW KIT
Build the same vendor intake review loop
Review the handbook, copy the workflow recipe, and use the Jodoo field model when adapting the Make workflow to your own vendor sources.
What your team can reuse
Make receives the vendor request through a Custom webhook, maps the review payload in an HTTP module, and records the operation in History. Jodoo keeps the durable procurement record for document, risk, owner, and approval follow-up.
Business workflowJodoo field modelAgent promptRollout checklist
REUSABLE WORKFLOW
The workflow decides. Jodoo keeps work moving.
- 01
Custom webhook
Receives the Atlas Packaging Co. bundle in Run once mode
- 02
Make scenario
A Make Custom webhook receives the vendor payload and an HTTP module posts structured fields to Jodoo.
- 03
HTTP module
Posts vendor review JSON and parses the bridge response
- 04
Scenario history
Shows success, operations, duration, and data transfer
- 05
Jodoo review app
Stores risk, recommendation, reviewer, and document follow-up
WORKFLOW LOOP
From Make webhook bundle to Jodoo vendor review
A Make Custom webhook receives a supplier intake bundle from a test request, form, or portal source.
Run once mode keeps the vendor bundle visible before the scenario is scheduled or activated.
The HTTP module maps supplier fields, missing document notes, risk level, recommendation, reviewer, and next action.
Make sends the JSON body to the Jodoo bridge and captures the response in scenario history.
Jodoo creates the vendor onboarding record and groups procurement work by document follow-up, risk, owner, and approval status.
The same visual scenario pattern can later add routers, filters, notifications, or connected source modules.
FIELD MAPPING
Agent output becomes Jodoo fields
| Agent or source data | Jodoo record fields |
|---|---|
| vendor_name, vendor_category, business_need | Vendor Legal Name, Vendor Category, Vendor Business Description |
| contact_name, contact_email | Primary Contact Name, Primary Contact Email |
| requested_by, suggested_owner | Requester Name, Compliance Reviewer |
| missing_documents, compliance_status | Document Completeness, Review Comments |
| risk_level, recommendation, review_status | Risk Level, Approval Recommendation, Onboarding Status |
AGENT RECIPE
Prompt and structured output
Make scenario role
Receive one supplier intake bundle through a Make Custom webhook and send a structured vendor review object into Jodoo.
Field preparation rule
Normalize missing documents, compliance status, recommendation, suggested owner, and review status before the HTTP module runs.
HTTP module contract
Use POST, JSON body content, response parsing, and a saved bridge URL before relying on scenario history as proof.
Required output
Return vendor_name, vendor_category, business_need, contact_email, requested_by, risk_level, missing_documents, recommendation, suggested_owner, next_best_action, and source_platform.
{
"vendor_name": "Atlas Packaging Co.",
"vendor_category": "Packaging supplier",
"contact_name": "Nora Patel",
"contact_email": "nora.patel@atlaspackaging.example",
"business_need": "Secondary packaging supplier for West Coast fulfillment.",
"requested_by": "Operations Procurement",
"spend_estimate": "120000 annual",
"risk_level": "Medium",
"compliance_status": "Needs W-9 and insurance certificate",
"missing_documents": "W-9, certificate of insurance, sustainability policy",
"recommendation": "Proceed with conditional review",
"suggested_owner": "Procurement Ops",
"next_best_action": "Request missing documents and schedule sourcing review",
"review_status": "Needs document follow-up",
"source_platform": "make",
"agent_confidence": "0.84"
}JODOO STARTER APP
Vendor intake review starter app
Use the field model, suggested views, and automation rules when adapting the vendor onboarding workflow for procurement teams.
Included fields
- Vendor legal name
- Vendor category
- Business need
- Primary contact
- Requester
- Compliance reviewer
- Document completeness
- Risk level
- Approval recommendation
- Onboarding status
- Review comments
- Original agent output
Suggested views
- Needs document follow-up
- Medium or high risk
- Owner queue
- Ready for sourcing review
- All vendor reviews
Automation rules
- Create a Jodoo vendor onboarding record after Make returns structured output.
- Move medium or high risk vendors into a compliance review queue.
- Notify the compliance reviewer when document completeness is partial.
- Keep the original workflow output in review comments or audit context.
ROLLOUT CHECKLIST
What to confirm before production
- Create the Make Custom webhook and run it once with synthetic supplier data.
- Confirm the webhook bundle fields match the Jodoo field mapping.
- Save the HTTP module after editing method, URL, headers, and JSON body.
- Check Make history for status, duration, operations, and response body.
- Add routers or filters only after the base vendor review writeback is stable.
- Move real supplier credentials and endpoint secrets into controlled connections.
IMPLEMENTATION REFERENCES
Keep the setup details for your team
Jodoo Starter App Blueprint
The Jodoo field model, recommended vendor views, sample payload, and writeback mapping used after the Make scenario completes.
Open blueprintAgent Prompt + Workflow Recipe
The Make webhook setup, HTTP request body, module save checks, scenario history validation, sample vendor payload, and Jodoo field mapping.
Open recipeWORKFLOW
From Make vendor review to Jodoo onboarding record
Make handles the visual scenario; Jodoo keeps the record procurement teams can filter, assign, and review.
A Make Custom webhook receives a supplier intake bundle from a test request, form, or portal source.
Run once mode keeps the vendor bundle visible before the scenario is scheduled or activated.
The HTTP module maps supplier fields, missing document notes, risk level, recommendation, reviewer, and next action.
Make sends the JSON body to the Jodoo bridge and captures the response in scenario history.
Jodoo creates the vendor onboarding record and groups procurement work by document follow-up, risk, owner, and approval status.
The same visual scenario pattern can later add routers, filters, notifications, or connected source modules.
JODOO RECORD
What Jodoo stores
Jodoo keeps the durable vendor review fields after the workflow runs: vendor name, business need, compliance reviewer, document completeness, risk, recommendation, and onboarding status.
Vendor legal nameVendor categoryBusiness needPrimary contactRequesterCompliance reviewerDocument completenessRisk levelApproval recommendationOnboarding statusReview commentsOriginal agent output
REAL TEST RUN
A Make workflow wrote the vendor review into Jodoo
The screenshots use synthetic vendor data and show the Make setup, a successful run, and the Jodoo row created by the workflow.
Scenario configuration
A Make Custom webhook receives the vendor payload and an HTTP module posts structured fields to Jodoo.
Successful Make run
The Make HTTP module completes successfully and the bridge returns a Jodoo data ID.
Jodoo writeback
The vendor review was written into a Jodoo vendor onboarding record with risk, recommendation, and compliance reviewer fields.
FAQ
Common questions
Answers about using agent platforms with Jodoo records, workflows, and app templates.
Was this Make vendor workflow tested end to end?
Yes. The proof used a Make Custom webhook, an HTTP module run, and a verified Jodoo writeback screenshot with a proof manifest.
Why use Make for vendor intake review?
Use Make when a visual scenario, Run once testing, bundle inspection, and module history matter to the operations team.
Does the first Make proof require an AI module?
No. The proof keeps the writeback path reliable first. Teams can add a Make AI or model step later when the output schema is stable.
What should be checked before production use?
Confirm operation limits, webhook ownership, error handling, source permissions, and the reviewer model before processing real supplier data.
What does Jodoo store after the Make run?
Jodoo stores vendor identity, document completeness, risk level, recommendation, compliance reviewer, onboarding status, and review comments.
NEXT STEP
Turn vendor intake into procurement follow-up
Start with one supplier request, then reuse the same writeback pattern for compliance review, supplier onboarding, contract intake, and purchase requests.