Run¶
For a custom client of a published chat, see Chat API and Third-party authentication.
Use React chat toolkit for components or Chat widget for a bubble on your website.
A workflow runs in six ways. All of them go through the same engine, produce the same trace, and appear in the run history (Run → View all).
| Started by | How | Badge in History |
|---|---|---|
| The editor | Run, Step or Run to here, over /ws/run |
— |
| Another service | POST /api/hooks/workflows/{wid}/runs with a workflow token |
API |
| An MCP client | The workflow's run_... tool at /mcp, with a workflow token |
API |
| A timetable | A cron schedule on the workflow | Schedule |
| A chat message | A command word to your Slack app or Telegram bot | Chat |
| A person resuming | Approve, reject or answer a waiting Human node | — |
-
The Logs timeline, stepping, cancel, limits and cost.
-
Waiting runs, notifications and chat approvals.
-
Tokens, sync and async runs, signed callbacks, workers.
-
Claude Desktop, Cursor and other agents call the workflow as a tool.
-
Cron, time zones and missed times.
-
A message to the Slack app or Telegram bot starts a run; the bot answers.
-
Chat with a workflow in the studio, with memory and its steps.
-
Test cases, Run all, comparison with earlier versions.