{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/workflow-automation.run-workflow-as-tool/",
    "json": "https://www.anchorterminal.com/niches/workflow-automation.run-workflow-as-tool/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/workflow-automation.run-workflow-as-tool/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/workflow-automation.run-workflow-as-tool/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 13 | 54 | 15 | 9 |\n\n## What counts as done\n\nThe published (not test) version runs once with the given input, the run appears in the platform's log, and the output or a pollable run ID returns within the client's tool timeout; a failed run comes back as an error, not a 200 with error text.\n\nHow agents ask for it: run the weekly report scenario; trigger the onboarding flow for this customer; call my n8n workflow with this input; run the enrich-lead script\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Activepieces API + MCP (Activepieces Inc.)**: The MCP tool list has test tools but no tool that runs a published flow; acc-14 reports ChatGPT test-running flows with no logged run. Sync webhooks run the published flow but close at 30 s, and issue 13334 reports silent 200/204 on timeout.\n- **Microsoft Copilot Studio MCP (Microsoft Corporation)**: The only run path is manage_workflows' real test of a published, enabled workflow, read back through list_runs and get_run; forwarded calls get a 36-minute deadline. It's a build bridge, not a tool surface for running named workflows, and each run costs credits.\n- **Gumloop (AgentHub Inc. (doing business as Gumloop))**: POST /agents/{id}/sessions returns 202 and a session to poll, with a caller session_id that 409s on repeat. Webhook triggers return success at once without output. There is no published-versus-test choice, and API access needs Pro.\n- **Kestra (Kestra Technologies SAS)**: McpToolTrigger registers a flow as a named MCP tool with inputs as schema and outputs returned, and executions take wait=true and kind=NORMAL. No MCP timeout is stated, and the docs don't show a failed execution returning an MCP error.\n- **Kognitos (Kognitos, Inc.)**: kognitos_invoke_automation takes stage PUBLISHED and an idempotency_key and returns a run to poll with kognitos_runs. A run can stop in waiting for a person, and failure arrives as run state on poll; no MCP error example is documented.\n- **Make API + MCP (Celonis, Inc.)**: MCP runs active and on-demand scenarios as tools with inputs and outputs; a call past 25 s (OAuth) or 40 s (key) returns an executionId to fetch later, and runs last up to 40 minutes. How a failed run reaches the client isn't documented.\n- **n8n API + MCP (n8n GmbH)**: execute_workflow takes executionMode production and returns an execution ID at once, polled with get_workflow_execution. An MCP Server Trigger failure came back without isError (acc-09), and a production webhook failed with no execution logged (acc-36).\n- **Paragon ActionKit + MCP (Forge Technology, Inc. (d/b/a Paragon))**: Request triggers and ActionKit's POST /tools run for one Connected User, and the docs' AI SDK example treats non-2xx as failure, but the listing records Run Tool returning 200 and dropping unknown parameters, and no run ID is described for ActionKit calls.\n- **Pipedream API + MCP (Pipedream, LLC)**: Existing workflows keep running on their triggers until the shutdown, and Connect runs single prebuilt actions as MCP tools with isError on failure, but a workflow itself isn't exposed as a tool and the product is ending.\n- **Microsoft Power Automate (Microsoft Corporation)**: The page documents no run call; an agent starts a flow only through an HTTP request trigger the owner added, and the run lands in the FlowRun table. Whether a failed run returns an error to the caller wasn't documented in what was read.\n- **Prismatic (Prismatic Software Inc.)**: The hosted MCP flow server lists agentic flows as tools with invocation schemas, scoped globally, per integration or per instance. Organisation members see only test instances; customer users see production ones. No timeout or failure shape is documented on the pages read.\n- **Tray.ai API + MCP (Tray.ai, Inc.)**: Agent Gateway exposes a workflow with an Agent Tool Trigger and Trigger Reply as one MCP tool returning structured results. Agent Gateway is an add-on, no timeout is stated, and the listing records upstream errors wrapped in a 200.\n- **Windmill API + MCP (Windmill Labs, Inc.)**: Scripts and flows as tools gives one typed tool per selected path, and the call waits for the result, but a wait that times out cancels the run unless the flow uses early return. acc-18 hit a separate 1,000-execution MCP cap (still open).\n- **Workato API + MCP (Workato, Inc.)**: Recipes can be turned into skills and MCP servers, and force_run starts an on-demand run, but the pages read don't say whether a tool call waits for the job or how a failed job reaches the caller.\n\n- not this job: Bind AI (1Fort Inc.): No MCP server or run endpoint for a named workflow; the API is the web app's backend behind a user JWT from sign-in or OTP.\n- not this job: Cooper (Mandl) (Cooper AI Tech, Inc.): No run endpoint, webhook or MCP tool is published.\n- not this job: Motive Agents (Motive Technologies, Inc.): Agents fire on Motive's own safety, maintenance and idling events; nothing lets an outside agent call one.\n- not this job: Node-RED (OpenJS Foundation): No run endpoint and no execution log; an agent can only call an HTTP In node the owner built, and nothing records that the run happened.\n\n## What stops agents finishing\n\n- tool call times out before the run finishes and no run ID is returned\n- client test-runs the flow instead of running the published version\n- separate MCP execution cap below the plan's run allowance\n- tool schema rejected by one model family (Gemini)\n- production webhook fails without logging an execution\n\n## Around it\n\nBefore: workflow-automation.build-workflow, chat.user-asks. After: email.send, crm.update-record, workflow-automation.debug-failed-run.\n\n## Where this comes from\n\nWeight 15 of 100 in Workflow automation: 9 of 48 accounts (n8n, Activepieces, Windmill, Kestra); MCP and webhook run failures in GitHub issues and the n8n forum\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/workflow-automation.run-workflow-as-tool.json, or the MCP tool get_use_case with id workflow-automation.run-workflow-as-tool. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Run an existing workflow as a tool and get its result",
        "url": ""
      }
    ],
    "description": "Run an existing workflow as a tool and get its result: 0 companies fully do it, 13 with a limit, 54 carry the tag. Every listing in Workflow automation with the reason and a source.",
    "facts": null,
    "h1": "Run an existing workflow as a tool and get its result",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/workflow-automation.run-workflow-as-tool/",
    "published": "",
    "section": "agents",
    "title": "Run an existing workflow as a tool and get its result | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/workflow-automation.run-workflow-as-tool/"
  },
  "tokens": {
    "markdown": 1800,
    "slim": 380
  },
  "version": 1
}
