Skip to main content
POST
Run Workflow
Triggers a workflow execution. This is the primary way to run workflows programmatically.

Usage

How It Works

  1. The API creates a WorkflowRequest with status pending
  2. The request is enqueued for processing
  3. Execution begins at the specified entry node(s)
  4. The entry node receives a payload: { "text": "<query>", "chat_id": "<chat_id>", "files": [...] }
  5. Downstream nodes access this via {{ start.text }}, {{ start.chat_id }}, etc.

Prerequisites

Before running a workflow, you need:
  1. A workflow version ID — Get it via List Workflows or Get Latest Version
  2. Entry node IDs — Get them via Get Entry Nodes
  3. A chat session — Create one via Create Chat

Response

Returns a workflow_request_id you can use to:

Rate Limit

20 workflow executions per minute per user.

Notes

Authentication required: The authenticated user must own the workflow or have access via a published agent.

Authorizations

Authorization
string
header
required

API token generated from your Splox account settings. Create tokens at https://app.splox.io/account?tab=settings

Body

application/json
workflow_version_id
string<uuid>
required

ID of the workflow version to execute

chat_id
string<uuid>
required

Chat session ID (used for context memory and SSE streaming)

entry_node_ids
string<uuid>[]
required

IDs of the entry nodes to begin execution at

query
string
required

The user message or query text. Available as {{ start.text }} in the workflow.

files
object[]

Optional file attachments. Available as {{ start.files }} in the workflow.

additional_params
object

Optional extra parameters merged into the payload

Response

Workflow execution started successfully

workflow_request_id
string<uuid>

ID of the created workflow request. Use this to listen for results, get the execution tree, or check status.