Skip to content
AdlyseMCP Docs
Product guideMCP reference
⌘K
Open Adlyse
⌘K
Overview
QuickstartAuthentication
adlyse-insights
adlyse-reports
adlyse-ads
adlyse-workflows
list_workflowsget_workflowrun_workflowget_run_status
adlyse-adminadlyse-all
  1. Overview
  2. adlyse-workflows

run_workflow

Trigger a workflow run. Runs are asynchronous — poll with get_run_status to retrieve the output.

Parameters#

NameTypeRequiredDefaultDescription
workflow_idstringyesWorkflow id
input_datastring | object | nullno{}Input matching the workflow’s input_schema. String values are parsed as JSON when possible; otherwise treated as raw input.

Returns#

json
{
  "run_id": "agent_run_xyz",
  "status": "pending"
}
FieldDescription
run_idPass to get_run_status to poll
statusInitial status: usually pending. Typical path: pending → running → completed

Errors#

error_typeWhen
auth_errorMissing / invalid API key
not_foundWorkflow id doesn’t exist or is outside your org
invalid_inputInput failed the workflow’s trigger-schema validation
execution_errorCouldn’t dispatch the run (rare — usually transient)

Example#

Request:

json
{
  "workflow_id": "agent_abc",
  "input_data": { "email": "lead@example.com" }
}

Response:

json
{ "run_id": "agent_run_xyz", "status": "pending" }

Then poll get_run_status until status is completed or failed.

See also#

  • get_workflow — inspect input_schema before calling
  • get_run_status — poll for completion
Previousget_workflowNextget_run_status