Walkthroughs
A walkthrough follows one concrete case from start to finish and shows what each component does at every step: which HTTP call the worker makes, what the engine checks, what PostgreSQL records and what happens when something fails halfway.
| If you want to… | Read |
|---|---|
| build something hands-on in Studio | the tutorials under Get started |
| understand how it works on a concrete case | these walkthroughs |
| look up the lifecycle, states and guarantees | Agent Worker execution |
| check the normative contract | Authoritative contracts |
The running example
Section titled “The running example”Every walkthrough uses the same support case so that the pieces connect:
- Alice (customer
C-42) writes: “My parcel never arrived” (order5531). - A
triageagent node reads her record from a CRM tool server (crm/get_customer, a read), opens a ticket (crm/create_ticket, a write), and may refund her €89 — either through an approval-required tool (crm/refund) or by delegating to arefund_payoutprocess. refund_payoutpays through a third-party payments worker built with the Java SDK.
The names crm, refund_payout and payments.payout are illustrations; the
mechanics are those of the engine and the first-party worker.
1. The Agent Worker, its SDK, tools and MCPThe three layers — SDK, worker, engine — and who is allowed to do what.
2. A CRM call and back to the engineOne read, one keyed write and the final answer, call by call.
3. Many instances at onceSlots, leases, SKIP LOCKED and what happens when two workers collide.
4. A refund that needs approvalapproval_required: the agent proposes, a person decides, the exact call runs once.
5. Delegating to a sub-processThe agent starts a governed child process and continues with its declared outputs.
6. Writing a third-party workerA payments worker with the Java SDK: fetch, heartbeat, complete, fail, BPMN error.