Executions API

Query workflow execution history, inspect individual execution results, and view per-node input/output data for debugging.

List Executions

GET

/api/executions/team/:teamId

List all executions for a team

Path Parameters

Parameter	Type	Description
`teamId`	UUID	The team to list executions for

Query Parameters

Parameter	Type	Required	Description
`page`	integer	No	Page number (default: 0)
`size`	integer	No	Page size (default: 20)
`status`	string	No	Filter by status: SUCCESS, FAILED, RUNNING, CANCELLED
`workflowId`	UUID	No	Filter by specific workflow
`from`	ISO 8601	No	Start date for filtering
`to`	ISO 8601	No	End date for filtering

Response

200 OK

{
  "content": [
    {
      "id": "uuid",
      "workflowId": "uuid",
      "workflowName": "Order Processing",
      "status": "SUCCESS",
      "startedAt": "2026-02-17T10:30:00.000Z",
      "finishedAt": "2026-02-17T10:30:02.350Z",
      "durationMs": 2350,
      "triggerType": "WEBHOOK",
      "nodeCount": 8,
      "errorMessage": null
    }
  ],
  "totalElements": 156,
  "totalPages": 8,
  "number": 0,
  "size": 20
}

Get Execution Details

GET

/api/executions/:id

Get detailed execution results including per-node data

Path Parameters

Parameter	Type	Description
`id`	UUID	The execution ID

Response

The response includes the execution summary plus a nodeExecutions array containing the input, output, status, and timing for each node that ran.

200 OK

{
  "id": "uuid",
  "workflowId": "uuid",
  "workflowName": "Order Processing",
  "status": "SUCCESS",
  "startedAt": "2026-02-17T10:30:00.000Z",
  "finishedAt": "2026-02-17T10:30:02.350Z",
  "durationMs": 2350,
  "triggerType": "WEBHOOK",
  "nodeExecutions": [
    {
      "nodeId": "uuid",
      "nodeName": "Webhook Trigger",
      "nodeType": "WEBHOOK_TRIGGER",
      "status": "SUCCESS",
      "startedAt": "2026-02-17T10:30:00.000Z",
      "finishedAt": "2026-02-17T10:30:00.120Z",
      "input": { "body": { "orderId": 42 } },
      "output": { "orderId": 42, "customer": "Acme Corp" },
      "errorMessage": null
    },
    {
      "nodeId": "uuid",
      "nodeName": "Validate Order",
      "nodeType": "IF_ELSE",
      "status": "SUCCESS",
      "startedAt": "2026-02-17T10:30:00.125Z",
      "finishedAt": "2026-02-17T10:30:00.130Z",
      "input": { "orderId": 42, "customer": "Acme Corp" },
      "output": { "branch": "true", "orderId": 42 },
      "errorMessage": null
    }
  ]
}

Debugging failed executions

When an execution has status: "FAILED", check the errorMessage field on both the top-level execution and individual node executions to pinpoint which node caused the failure.

Execution Statuses

Status	Description
`RUNNING`	The execution is currently in progress
`SUCCESS`	All nodes completed without errors
`FAILED`	One or more nodes encountered an error
`CANCELLED`	The execution was manually cancelled or timed out

Error Codes

Status	Meaning
`403`	User does not have access to this team
`404`	Execution not found

Workflows

Credentials