Skip to main content
POST
/
public
/
@
{nickname}
/
workflows
/
{slug}
/
versions
/
{versionID}
/
trigger
Trigger public workflow version
curl --request POST \
  --url https://workflows.eachlabs.run/api/v1/public/@{nickname}/workflows/{slug}/versions/{versionID}/trigger \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "version_id": "v1",
  "inputs": {
    "text": "tell me a story"
  },
  "webhook_url": "https://your-api.com/webhooks/workflow-completed"
}
'
{
  "execution_id": "e2dba2bb-bc1d-4651-b6bf-fbbbebdee104",
  "status": "queued",
  "started_at": "2025-12-03T10:21:09Z"
}

Documentation Index

Fetch the complete documentation index at: https://docs.eachlabs.ai/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
X-API-Key
string
header
required

API key for authentication

Path Parameters

​
nickname
string
required

Organization nickname (without @ prefix)

Example:

"acme-corp"

​
slug
string
required

Workflow slug

Example:

"my-image-generator"

​
versionID
string
required

Version identifier

Example:

"v1"

Body

application/json
​
version_id
string

Optional: Specific version to trigger.

If not provided, triggers the latest version of the workflow. This allows you to execute specific versions for testing or comparison.

Example:

"v1"

​
inputs
object

Input parameters defined in the workflow definition for the workflow

Example:
{ "text": "tell me a story" }
​
webhook_url
string<uri>

Optional webhook URL for execution completion notifications.

When provided, the engine will POST an ExecutionDetails payload to this URL when the workflow finishes (either successfully or with an error).

See the Webhooks section for detailed information about webhook behavior and payload structure.

Example:

"https://your-api.com/webhooks/workflow-completed"

Response

Workflow execution started

Response from triggering a workflow execution

​
execution_id
string

Unique execution identifier (only present for successful triggers)

Example:

"exec_xyz789"

​
status
enum<string>

Execution status immediately after triggering.

  • queued: Workflow execution has been queued and will start shortly
  • failed: Trigger failed due to validation or system error
Available options:
queued,
failed
Example:

"queued"

​
started_at
string<date-time>

RFC3339 timestamp when the execution was queued (only present for successful triggers)

​
message
string

Error message (only present when status is "failed")

Example:

"invalid input: missing required field"

Last modified on May 28, 2026