Invoice email from a vendor
Input: Vendor name and invoice text
Operations template · 10 steps
Invoices are read with fixed patterns, routed to the right approver by amount and recorded once signed off.
Highlighted: the path taken by the “Small invoice” sample after approval.
Input: Vendor name and invoice text
Every write and send waits for a human approval first.
{
"vendor": "Paper Mill Supplies (Demo)",
"vendor_email": "billing@papermill-demo.com",
"body": "Invoice INV-2291. Amount due: 1,240.50. Due on 2026-11-30."
}| # | Step | Type | What it does |
|---|---|---|---|
| 01 | Invoice email | Trigger | Where a run starts: a form, email, call, schedule or other event. |
| 02 | Read invoice | Transform | Reshapes data with a fixed, safe operation. No custom code runs. |
| 03 | Readable? | Condition | Sends the record down the true or false branch based on your rules. |
| 04 | Over 5,000? | Condition | Sends the record down the true or false branch based on your rules. |
| 05 | Ask vendor to resend | Draft message | Writes a message from a template and the record. It is a draft until a Send step. |
| 06 | Finance director | Human approval | Pauses the run until a person approves or rejects. Required before sends and writes. |
| 07 | Accounts clerk | Human approval | Pauses the run until a person approves or rejects. Required before sends and writes. |
| 08 | Sent back | End | Marks a finished branch and names the outcome. |
| 09 | Record in ledger | CRM write | Writes a row to the synthetic CRM, with retries and a dead-letter queue. |
| 10 | Ready to pay | End | Marks a finished branch and names the outcome. |
Under 5,000, so the accounts clerk approves.
Result: Invoice approved and recorded
Over 5,000, so it waits for the finance director.
Result: Invoice approved and recorded
No amount or number found, so a resend request is drafted.
Result: Unreadable invoice, resend request drafted