Getting started paths
What this section is
Paths are end-to-end routes through ArcFlow for different roles and deployment shapes. Each path is a self-contained document you can finish in one sitting. Pick the path that matches how you plan to run workflows, then follow the linked integrating lessons when you need server, HITL, or external callback behavior.
ArcFlow services (quick map)
Choose a path
| Path | Audience | Time | Outcome |
|---|
| First workflow in five minutes | Developer | ~5 min | Two-agent workflow in Python, no Docker |
| Python quickstart | Developer | ~20 min | Install, default run, optional OpenAI, traces |
| TypeScript quickstart | Developer | ~20 min | Node SDK, async patterns, parity with Python |
| Server API quickstart | Platform / backend | ~30 min | Docker stack, curl create/poll/trace |
| Static site chatbot | Frontend + platform | ~45 min | Server, ingest, publish, Relay embed |
Recommended order
If you are new to ArcFlow:
- First workflow in five minutes to confirm SDK wiring.
- Python quickstart or TypeScript quickstart for traces and optional live providers.
- Integrating track when you need HTTP server, callbacks, or HITL.
- Static site chatbot when you ship a browser chat widget with Relay.
Before any path
Install the SDK or confirm Docker depending on your path:
After these paths