# AI Purchase Request Approval Routing with n8n + Jodoo

## Use Case

Procurement teams need approval route, budget confirmation, quote status, owner, and next action before sourcing starts.

## Workflow Pattern

1. Webhook node receives the source request or payload.
2. n8n prepares a structured purchase request decision.
3. HTTP Request node sends the mapped output to the Jodoo writeback endpoint.
4. Jodoo stores the operational record for queue review, ownership, and follow-up.

## Proof Record

- Jodoo data ID: `6a27a52e7a63856d6cf9d279`
- Record anchor: `Twelve rugged tablets for the field service team, including protective cases and device enrollment support.`
- Jodoo app: Purchase Request Form

## What Jodoo Keeps

Jodoo stores requester, department, item, quantity, estimated total, budget code, approval route, sourcing status, owner, missing information, and next action.

## How to Adapt

- Start with a synthetic sample, then replace it with your own intake source.
- Keep the n8n trigger and action names visible so the workflow is easy to rebuild.
- Keep the Jodoo fields specific to the review queue your team will actually use.