Skip to main content
POST
Execute workflow and wait for the result

Authorizations

X-Api-Key
string
header
required

Path Parameters

workflowId
string<uuid>
required

The ID of the workflow to execute

Body

application/json

Execution request parameters

Request to execute a workflow and wait for the result

agentProfileId
string<uuid>

The ID of the agent profile to use for this execution. Mutually exclusive with agentProfilePoolId.

agentProfilePoolId
string<uuid>

The ID of the agent profile pool to select a profile from. Mutually exclusive with agentProfileId.

dynamicData
object
deprecated

Deprecated: Use 'inputs' instead. Inputs to be merged into the placeholders defined in prompts

executionOptions
object

Per-execution runtime options that override or extend the workflow's default settings.

inputs
object

Inputs to be merged into the placeholders defined in prompts

metadata
object

Optional metadata key-value pairs (string keys and string values) for organizing and filtering executions

onCapacityLimit
enum<string>

What to do when the execution cannot start right now because the organisation is at its concurrency limit or every profile in the pool is in use. "reject" (the default) fails the request as today. "queue" accepts it: the execution is created in the "queued" status under the returned ID and starts automatically, oldest first, as capacity frees. Temp files cannot be queued.

Available options:
reject,
queue
tempFiles
object[]

Array of temporary files to attach to the execution. Must have been pre-uploaded using the stage file endpoint

timeoutSeconds
integer
default:25

Seconds to wait for the execution to finish before returning 202. Defaults to 25.

Required range: 1 <= x <= 25
version
integer

The version of the workflow to execute. If not provided, the published version is used.

Response

The request has succeeded.

Response from executing a workflow and waiting for the result

executionId
string<uuid>
required

The ID of the newly created execution

status
enum<string>
required

The execution's status when the call returned: terminal on 200, the current status on 202

Available options:
queued,
starting,
running,
paused,
awaiting_confirmation,
completed,
cancelled,
failed,
paused_by_agent
executionResult
object

Outcome, reasoning and result data. Present on 200 when the execution recorded a result.