Resume waiting workflow execution
Resume a workflow execution that is in ‘waiting’ status. Workflows enter waiting status when they reach a wait_for_response step or are explicitly paused.
Send a message with:
kind: Message type, defaults to “payload” if omitteddata: The actual payload - can be a string for simple text responses (e.g., “yes”, “no”) or an object for structured data (e.g., button clicks, form submissions)
Optionally include variables to update the execution context:
variables: Key-value pairs to merge into the execution context. These will be available in subsequent workflow steps as{{var_name}}. Existing variables with the same key will be overwritten.
After resuming, the workflow will continue processing from the waiting step with the provided message data and updated variables.
Call workflow routing: If the execution is waiting at a call workflow step, the input is routed to the child execution it started, following the chain down to the deepest waiting execution. Keep sending resumes to the original execution ID; the response reports where the input landed in id, echoes the requested ID in requested_execution_id, and includes parent_flow_execution_id.
Response: Returns minimal execution data (id, status, tracking_id, timestamps, workflow, current_step) plus the routing fields. Does not include execution_context or events. Use GET /workflow_executions/ to retrieve full execution details.
Body
Request to resume a workflow execution that is in 'waiting' status. Executions wait when they reach a wait_for_response step or when explicitly paused. The message data can be a simple string for text responses or a structured object for complex interactions.
You can optionally include variables to update the execution context with new or modified variables that will be available to subsequent workflow steps.

