Integrating ArcFlow
What this track is
The integrating track is for teams that have run a local stub workflow and now need to choose how ArcFlow fits their stack. The lessons compare embedded SDK runs with server-backed HTTP execution, walk through a first server API call, and introduce the two pause patterns that require Postgres: external callbacks and human-in-the-loop (HITL) approval.
Nothing here replaces the full guides under documentation/guides/. These pages are short introductions with one runnable example each and pointers to normative detail.
How to use it
Read the lessons in order if you are deciding deployment shape for the first time. Skip lesson 1 if you already know you need the HTTP server. Each page includes a Verify section so you can confirm behavior before moving on.
| Order | Lesson | What you learn |
|---|---|---|
| 1 | Embedded SDK vs server | When to embed the runtime vs call arcflow-server |
| 2 | Server API first run | Docker stack, POST /v1/runs, poll, trace |
| 3 | External callbacks intro | ExternalOutcome.report / report_outcome lifecycle |
| 4 | HITL approval intro | Interrupt, approve, resume on the server |
Before you start
Complete at least one path from Getting started paths:
| Path | Document |
|---|---|
| Fastest local run | First workflow in five minutes |
| Python SDK detail | Python quickstart |
| HTTP without SDK | Server API quickstart |
For server lessons (2 through 4), you need Docker with Compose v2 and ports 8080 and 5432 available on your machine.
After this track
| Goal | Document |
|---|---|
| Full external callback guide | External callbacks |
| Webhook HMAC verification | Webhook security |
| HITL configuration detail | Configuring interrupts |
| HITL approve API | Approve and reject |
| Guided server tutorial | Track B: Server API |
| HITL and external tutorial | Track E: HITL and external |
| Static site product | Static site chatbot |