Stream Workflow Events
Available for: Chatflow, Workflow apps.
Resume the Server-Sent Events stream for a workflow run after a pause or a dropped SSE connection. For runs that have already finished, the stream emits a single workflow_finished event and closes.
To check an in-progress run’s node-level status and progress, call it with include_state_snapshot=true: the stream replays each already-executed node’s status before streaming new events.
Authorizations
API Key authentication. For all API requests, include your API Key in the Authorization HTTP Header, prefixed with Bearer . Example: Authorization: Bearer {API_KEY}. Strongly recommend storing your API Key on the server-side, not shared or stored on the client-side, to avoid possible API-Key leakage that can lead to serious consequences. Requests with a missing or invalid API key fail with HTTP 401 and error code unauthorized.
Path Parameters
The workflow run ID (the workflow_run_id from the original run response) whose event stream to resume.
Query Parameters
End-user identifier that originally triggered the run. Must match the creator of the workflow run.
When true, replay from the persisted state snapshot to include a status summary of already-executed nodes before streaming new events.
Set to true to keep the stream open across multiple workflow_paused events (useful when the workflow has more than one Human Input node in sequence). Default closes the stream after the first pause.
Response
Server-Sent Events stream. Each event is delivered as data: {JSON}\n\n. Event payloads follow the same schemas as the original streaming response.
SSE stream of events from a resumed workflow run, in the same format as Run Workflow (Workflow apps) or Send Chat Message (Chatflow apps). When the resumed portion runs an LLM node with reasoning_format: separated, this stream also carries reasoning_chunk events.