Overview
The Executions API provides endpoints to monitor workflow executions, view their results, retry failed executions, and stop running workflows. Every time a workflow runs, an execution record is created with detailed information about the run.List Executions
Retrieve a paginated list of workflow executions.Query Parameters
Pagination cursor from previous response’s
nextCursorNumber of executions to return (max: 250)
Filter by execution status:
success, error, running, waiting, canceledInclude full execution data in response (significantly increases response size)
Filter executions by workflow ID
Filter executions by project ID
Return executions after this execution ID
Example Request
Response
Array of execution summary objects
Unique execution identifier
ID of the workflow that was executed
Name of the executed workflow
Execution status:
success, error, running, waiting, canceled, crashedExecution mode:
manual, trigger, webhook, retryISO 8601 timestamp when execution started
ISO 8601 timestamp when execution finished, or null if still running
Execution ID this is a retry of, or null
ID of successful retry, or null
Cursor for next page, or null if no more results
Number of currently running executions
Example Response
Get Execution
Retrieve detailed information about a specific execution.Path Parameters
The execution ID
Query Parameters
Include full execution data and node outputs
Example Request
Response
Execution ID
Workflow ID
Execution status
Execution mode
Start timestamp
Stop timestamp
Example Response
Setting
includeData=true returns the full execution data including all node inputs and outputs. This can be a very large response for complex workflows.Stop Execution
Stop a currently running execution.Path Parameters
The execution ID to stop
Example Request
Response
Returns the stopped execution object withstatus: "canceled".
Stop Many Executions
Stop multiple running executions based on filters.Request Body
Filter criteria for executions to stop
Filter by workflow ID, or “all” for all workflows
Array of statuses to stop:
["running", "waiting", "queued"]ISO 8601 timestamp - only stop executions started after this time
ISO 8601 timestamp - only stop executions started before this time
Example Request
Response
Retry Execution
Retry a failed or canceled execution.Path Parameters
The execution ID to retry
Request Body
Whether to load the latest workflow version (true) or use the original version (false)
Example Request
Response
Returns a new execution object with the retry information:- Only failed, canceled, or crashed executions can be retried
- The retry creates a new execution linked to the original via
retryOf - Setting
loadWorkflow: trueuses the current workflow version, which may differ from the original execution
Delete Execution
Permanently delete an execution and its data.Request Body
Array of execution IDs to delete
Example Request
Response
Update Execution
Update execution metadata such as annotations.Path Parameters
The execution ID to update
Request Body
Example Request
Response
Returns the updated execution object.Execution Status Values
Executions can have the following status values:Execution completed successfully without errors
Execution failed with an error in one or more nodes
Execution is currently in progress
Execution is waiting for an external event or condition
Execution was manually stopped by a user
Execution crashed unexpectedly (system error)
Execution is queued and waiting to start
Common Patterns
Monitor Workflow Execution
Clean Up Old Executions
Retry All Failed Executions
Error Responses
404 Not Found
409 Conflict
400 Bad Request
Next Steps
Workflows API
Manage workflows programmatically
Credentials API
Manage workflow credentials
Execution Data
Learn about execution data structure
Error Handling
Handle execution errors