v1

latestOpenAPI 3.1.02026-07-22115189303.8 KB

Workflows

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 omitted
data: 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.

Response: Returns minimal execution data (id, status, tracking_id, timestamps, workflow, current_step). Does not include execution_context or events. Use GET /workflow_executions/{id} to retrieve full execution details.

post/workflow_executions/{execution_id}/resume

Request body

variablesobject

Optional variables to merge into the execution context. These variables will be added to the vars section of the execution context, making them available throughout the workflow. New variables are merged with existing ones - duplicate keys will be overwritten with new values.

Example request

{
  "message": {
    "kind": "payload",
    "data": "yes, proceed"
  },
  "variables": {
    "estado": "retomado",
    "custom_var": 123,
    "user_response": "confirmed"
  }
}

Response

Execution resumed successfully