{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/workflow-automation.connect-app-accounts/",
    "json": "https://www.anchorterminal.com/niches/workflow-automation.connect-app-accounts/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/workflow-automation.connect-app-accounts/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/workflow-automation.connect-app-accounts/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 | 25 | 8 | 5 |\n\n## What counts as done\n\nEach app the workflow uses has a working connection created through the API or a hosted connect link, the connection's scopes cover every action the workflow calls, and one harmless test call per app succeeds.\n\nHow agents ask for it: connect my HubSpot so the flow can run; set up the Gmail credential; the client needs to connect their Salesforce\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.)**: REST has Upsert Connection and the embed SDK's connect() opens a hosted dialog, and ap_list_connections reads ACTIVE, MISSING or ERROR. API keys need the Platform edition, MCP refuses to handle secrets, and connector scopes against actions aren't documented.\n- **Microsoft Copilot Studio MCP (Microsoft Corporation)**: copilot_studio_prepare_connection and setup_connection create or repair real Power Platform connections after approval, by server-side SSO or browser consent; typed-credential connectors go to the UI. Scope coverage per action isn't documented.\n- **Gumloop (AgentHub Inc. (doing business as Gumloop))**: List MCP server tools returns gumloop_auth_url when a connector isn't connected, and List connected accounts reads them back, but scopes per connector aren't readable through the API.\n- **Kognitos (Kognitos, Inc.)**: Workspace book connections can be created, authorised, listed and read through the API, with connections:batchGet and user-info, but OAuth books still need the account owner at a consent screen, and scopes aren't read back.\n- **Make API + MCP (Celonis, Inc.)**: Create connection, Verify connection and editable-data-schema are in the API, but OAuth connections need a person to log in to Make and authorise, and an update with a missing field writes it empty.\n- **n8n API + MCP (n8n GmbH)**: credential:create and credential:read scopes let an agent create key-type credentials through the API and list_credentials reads them back, but OAuth credentials need a person, imported workflows need each credential set by hand (acc-34), and API keys travel by email (acc-35).\n- **Node-RED (OpenJS Foundation)**: Node credentials go inline or as a separate credentials object on POST /flows, so key-type accounts can be set by API; there is no OAuth connection manager or scope read-back.\n- **Paragon ActionKit + MCP (Forge Technology, Inc. (d/b/a Paragon))**: The Connect Portal, or the headless SDK, runs managed OAuth or API-key install per end user and getUser returns credentialStatus. Granted scopes per action aren't read back, and a person must complete the consent step.\n- **Pipedream API + MCP (Pipedream, LLC)**: Connect Link and the frontend SDK create managed-OAuth accounts per external user, readable through the accounts API. acc-28 shows a connector's OAuth omitting a scope its own List Messages tool needs.\n- **Prismatic (Prismatic Software Inc.)**: createCustomerCredential, connection templates and the config wizard set per-customer connections, including OAuth in a hosted wizard, but scopes per action aren't read back, and a failed mutation still returns 200.\n- **Tray.ai API + MCP (Tray.ai, Inc.)**: Headless can create an authentication request and check its completion, and existing authentications are listed and reused, but a person completes consent and granted scopes aren't read back per action.\n- **Windmill API + MCP (Windmill Labs, Inc.)**: The API has OAuth create_account, client-credentials connect and resources/create, so an agent can create key-type resources, but OAuth accounts need a person at consent and scope read-back wasn't found.\n- **Workato API + MCP (Workato, Inc.)**: The Connections API lists, creates, updates and disconnects connections, and PUT recipes/:id/connect binds one to a recipe, but OAuth connections need a person and scopes per action aren't read back.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Microsoft Power Automate (Microsoft Corporation)**: The flows-with-code page covers connection references inside clientdata but not creating the connections themselves, and the connection docs weren't read.\n\n- not this job: Bind AI (1Fort Inc.): Google and Office 365 mailbox connect endpoints exist for the broker's own inbox, not connections a workflow chooses; carrier and AMS connections go through onboarding.\n- not this job: Kestra (Kestra Technologies SAS): No connection object or hosted connect link; plugin credentials are secrets in configuration or the Enterprise secret store, with no scope read-back.\n- not this job: Cooper (Mandl) (Cooper AI Tech, Inc.): Apps are connected by a person clicking connect in Cooper; no connection API or hosted link for a workflow.\n- not this job: Motive Agents (Motive Technologies, Inc.): No connection API for Agents.\n\n## What stops agents finishing\n\n- connection needs a person at a consent screen\n- connector's OAuth omits a scope its own tools need\n- API-key-only apps leave keys in email\n- tokens are not exported when moving platforms\n\n## Around it\n\nBefore: workflow-automation.build-workflow. After: workflow-automation.run-workflow-as-tool, workflow-automation.unattended-sync.\n\n## Where this comes from\n\nWeight 8 of 100 in Workflow automation: 5 of 48 accounts (n8n forum agencies, Pipedream MCP scope gap, migration threads)\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/workflow-automation.connect-app-accounts.json, or the MCP tool get_use_case with id workflow-automation.connect-app-accounts. 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": "Authorise the app connections a workflow needs",
        "url": ""
      }
    ],
    "description": "Authorise the app connections a workflow needs: 0 companies fully do it, 13 with a limit, 25 carry the tag. Every listing in Workflow automation with the reason and a source.",
    "facts": null,
    "h1": "Authorise the app connections a workflow needs",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/workflow-automation.connect-app-accounts/",
    "published": "",
    "section": "agents",
    "title": "Authorise the app connections a workflow needs | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/workflow-automation.connect-app-accounts/"
  },
  "tokens": {
    "markdown": 1650,
    "slim": 380
  },
  "version": 1
}
