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

create_workflow

Create a new workflow in your organization from a JSON node/edge graph. Call get_workflow_schema first to learn the format. Always run with preview: true first, resolve any validation_errors, then call again with preview: false to persist.

Parameters#

NameTypeRequiredDefaultDescription
namestringyesWorkflow name
descriptionstringno""Short description
task_descriptionstringno""What the workflow does
node_configarray | stringnoJSON array of node objects (or a JSON string). See get_workflow_schema for per-node-type data fields.
edge_configarray | stringnoJSON array of edge objects (or a JSON string)
node_credentialsobjectno{node_id: account_id} map for credentialed nodes — ids from list_authoring_resources
usecasestringno"default"Workflow usecase key
previewbooleannofalseIf true, build + validate inside a rolled-back transaction and return validation results without persisting

Returns#

On preview:

json
{ "preview": true, "valid": false, "validation_errors": ["node_2: unknown llm_model"], "name": "Enrich Contact", "node_count": 3, "edge_count": 2 }

On apply:

json
{ "id": "agent_abc", "name": "Enrich Contact", "valid": true, "validation_errors": [], "url": "https://app.adlyse.com/workflows/agent_abc" }

Errors#

error_typeWhen
auth_errorMissing / invalid API key
validation_errorMalformed node_config / edge_config JSON, missing name

See also#

  • get_workflow_schema — the graph contract
  • update_workflow — iterate on the result
  • run_workflow — smoke-test with target="draft"