# Build or edit a workflow from a description

> Build or edit a workflow from a description: 0 companies fully do it, 13 with a limit, 47 carry the tag. Every listing in Workflow automation with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/workflow-automation.build-workflow/
- Markdown: https://www.anchorterminal.com/niches/workflow-automation.build-workflow/index.md (~2,000 tokens)
- Slim: https://www.anchorterminal.com/niches/workflow-automation.build-workflow/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/workflow-automation.build-workflow/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 13 | 47 | 21 | 13 |

## What counts as done

A workflow created through the API or MCP that passes the platform's own validation, is published, and completes one real or test run with the expected output, with no unrelated nodes changed.

Measured, for our own tests: this takes at most 10 tool calls.

How agents ask for it: build me an n8n workflow that sends new leads to HubSpot and Slack; add a step to this flow that writes to the sheet; turn this description into a Make scenario; edit the function node in my Node-RED flow and deploy it

## Does the job, with a limit

It 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.

- **Activepieces API + MCP (Activepieces Inc.)**: ap_build_flow, ap_validate_flow, ap_lock_and_publish and ap_test_flow cover build, check, publish and a test run over MCP, but connections are set up by a person in the UI (ap_setup_guide), so a flow needing app auth can't finish unaided.
- **Microsoft Copilot Studio MCP (Microsoft Corporation)**: manage_workflows has create, update, validate, get_publish_status and real tests in the 1.0.4 bundle, but saves are drafts, tests run published, enabled workflows with real effects, and credits are charged from the start of building.
- **Gumloop (AgentHub Inc. (doing business as Gumloop))**: Create agent, update agent, attach MCP servers and create schedule or webhook triggers are in the API and MCP, but the result is a prompt-driven agent with no validate call, app triggers are UI-only, and connectors need a person to sign in.
- **Kestra (Kestra Technologies SAS)**: POST /flows/validate, create or PUT one flow by namespace and id, then POST /executions with wait=true is three or four calls. But app credentials are secrets the owner sets (environment or Enterprise secret store), so a new HubSpot or Slack flow can't run until they exist.
- **Kognitos (Kognitos, Inc.)**: kognitos_create_automation builds from a plain-English description through Kognitos' own AI, then :validatePublish lists missing credentials, :publish, and invoke with a DRAFT stage tests it. The definition is written by Kognitos' builder, not the agent, and connections must be authorised first.
- **Make API + MCP (Celonis, Inc.)**: Create scenario takes a blueprint, Check module data and the isinvalid flag check it, then activate and run. Management tools need a paid plan, Update replaces the whole blueprint, and OAuth connections need a person in Make.
- **n8n API + MCP (n8n GmbH)**: validate_workflow, create_workflow_from_code, atomic partial update_workflow, publish_workflow and test_workflow cover it in a few calls, but API-created sub-workflows fail where editor-built ones run (acc-10), publish returned a false 404 (acc-11), and credentials need a person.
- **Node-RED (OpenJS Foundation)**: POST /flow adds a tab and PUT /flow/:id replaces one, and POST /flows takes a rev with Node-RED-Deployment-Type nodes or flows. There is no validate call or run API, a full deploy emptied wires on unrelated nodes (acc-23), and some workplaces ban agents (acc-48).
- **Paragon ActionKit + MCP (Forge Technology, Inc. (d/b/a Paragon))**: Paragraph defines workflows as TypeScript and the para CLI validates and pushes them, so an agent can author one, but deploy and per-user enablement go through the CLI and dashboard rather than an API, and Test Workflow runs in the editor.
- **Microsoft Power Automate (Microsoft Corporation)**: Create a workflows row with category 5 and clientdata, then PATCH statecode to 1 to turn it on. There is no validate call, clientdata is one encoded JSON string with connection references built by hand, flows under My flows are out of scope, and no API runs the flow.
- **Prismatic (Prismatic Software Inc.)**: validateIntegrationSchema checks a YAML definition, importIntegration and publishIntegration save and release it, and testIntegrationFlow runs it; the Prism MCP dev server wraps init, import and test. Mutations fail as HTTP 200 with an errors array, and deploying needs a customer instance with connections.
- **Tray.ai API + MCP (Tray.ai, Inc.)**: Headless MCP creates a workflow with its trigger, adds and updates single steps, validates every mutation server-side plus a whole-workflow audit, and runs it. New authentications need a person to finish the request, and the only test is a live run with real side effects.
- **Windmill API + MCP (Windmill Labs, Inc.)**: Build and run access writes scripts and flows as drafts, test-runs, diffs and deploys from the client; acc-19's parent_hash block was fixed in August 2026. Resources holding app credentials, and OAuth accounts, still need a person before a new flow can run.
- **Workato API + MCP (Workato, Inc.)**: AIRO MCP creates and edits recipes with step-level operations, field mapping and connections, and the Developer API creates, updates and starts recipes. No validate call was found in what was read, and OAuth connections need a person before the recipe can run.

- not this job: Bind AI (1Fort Inc.): Bind AI runs its own broker procedures from the inbox. The 1Fort API (453 paths) covers applications, quotes, billing and automation defaults per broker, with no endpoint that defines or publishes a workflow.
- not this job: Cooper (Mandl) (Cooper AI Tech, Inc.): Cooper is an insurance coworker staff use in its web workspace; llms.txt and the integrations page list no API, MCP server or workflow definition an agent could create.
- not this job: Motive Agents (Motive Technologies, Inc.): The launch post says fleet admins build Agents from triggers and actions in Motive; goal-based building is for early 2027. The developer portal lists fleet data APIs and webhooks, with no Agents endpoint.
- not this job: Pipedream API + MCP (Pipedream, LLC): Pipedream Workflows is in maintenance mode with no new signups (acc-46), and its data is deleted on 30 April 2027; the docs now offer export for rebuilding elsewhere, not building.

## What stops agents finishing

- flows created through the API behave differently from editor-built ones (n8n sub-workflows, publish 404)
- MCP tool schema rejects valid calls (Windmill createScript parent_hash)
- full redeploy silently changes unrelated nodes
- credentials do not bind, so a built flow cannot run until a person connects accounts
- the workplace bans coding agents from the platform

## Around it

Before: chat.user-describes-task, search.find-api-docs. After: workflow-automation.run-workflow-as-tool, workflow-automation.connect-app-accounts.

## Where this comes from

Weight 21 of 100 in Workflow automation: 13 of 48 accounts (n8n, Windmill, Node-RED, Make); the most common agent-specific job in GitHub issues and the n8n and Node-RED forums

As data: https://www.anchorterminal.com/api/v1/use-cases/workflow-automation.build-workflow.json, or the MCP tool get_use_case with id workflow-automation.build-workflow. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
