# n8n Workflow Recipe: Vendor Intake Review to Jodoo

This recipe shows the n8n proof structure for reviewing a vendor intake request and creating a Jodoo vendor review record. Adapt the trigger source and endpoint before using it with production supplier data.

## Input Contract

The workflow can receive a vendor request or an already-normalized review object.

```json
{
  "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": "n8n",
  "agent_confidence": "0.84"
}
```

## Agent Or Transformation Instruction

Review the vendor request and return one structured vendor review object that a procurement team can track in Jodoo.

Rules:

- Return one JSON object per vendor request.
- Do not invent tax, insurance, banking, or compliance documents that are not supported by the request.
- If required documents are missing, set `review_status` to `Needs document follow-up`.
- Use one of these risk values: `Low`, `Medium`, `High`.
- Use one of these recommendations: `Proceed with conditional review`, `Proceed`, `Reject`, `Needs more information`.
- Keep `source_platform` set to `n8n`.

Required JSON keys:

```json
{
  "vendor_name": "",
  "vendor_category": "",
  "contact_name": "",
  "contact_email": "",
  "business_need": "",
  "requested_by": "",
  "spend_estimate": "",
  "risk_level": "",
  "compliance_status": "",
  "missing_documents": "",
  "recommendation": "",
  "suggested_owner": "",
  "next_best_action": "",
  "review_status": "",
  "source_platform": "n8n",
  "agent_confidence": ""
}
```

## n8n Workflow Shape

1. Configure a Webhook trigger connected to an HTTP Request node.
2. Send the sample vendor payload for Atlas Packaging Co.
3. Keep or transform the payload into the required JSON keys.
4. Set method to `POST`.
5. Set body content type to `application/json`.
6. Send the structured object to the Jodoo writeback endpoint for `/jodoo/n8n/vendor-intake-review`.
7. Listen for a test event, then execute the HTTP Request node.
8. Confirm the response returns `ok: true` and a Jodoo data ID.
9. Open Jodoo and verify vendor name, risk level, document completeness, approval recommendation, and compliance reviewer.

## Jodoo Mapping

- `vendor_name` -> Vendor Legal Name
- `vendor_category` -> Vendor Category
- `business_need` -> Vendor Business Description
- `contact_name` -> Primary Contact Name
- `contact_email` -> Primary Contact Email
- `requested_by` -> Requester Name
- `suggested_owner` -> Compliance Reviewer
- `review_status` -> Onboarding Status
- `missing_documents` -> Document Completeness
- `risk_level` -> Risk Level
- `recommendation` -> Approval Recommendation
- `next_best_action` -> Review Comments
- `compliance_status` -> Review Comments
- Full JSON output -> Original Agent Output or Review Comments, depending on your Jodoo field model