Skip to main content

Execute workflow​

Manually trigger workflow execution. Execution is asynchronous (tree-based execution publishes starting-action commands and returns) — the verdict is not in this response; poll GET /workflows/{workflow_id}/executions/{execution_id}.

Path Parameters
  • workflow_id string required

    Workflow identifier

Header Parameters
  • SlashID-OrgID string required

    The organization ID

    Example: af5fbd30-7ce7-4548-8b30-4cd59cb2aba1
Request Body

Optional. Existing callers that send no body keep working, defaulting to a live run with no subject identity. A caller that DOES send a body must include mode, so the request states explicitly whether it starts a live run or a dry run.

  • identity_id string

    Neo4j entity_id of the subject identity. Required for a JML workflow; ignored for a raw workflow whose data input selects its own items.

  • mode string required

    Possible values: [live, dry_run]

    Controls whether an execution publishes outbound provider events. dry_run resolves and records every step identically to a live run but suppresses outbound publication at the publish boundary. Empty (on an existing execution) means live.

Responses

Workflow execution accepted


Schema
  • execution_id string