# Authorise the app connections a workflow needs

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

- Canonical: https://www.anchorterminal.com/niches/workflow-automation.connect-app-accounts/
- Markdown: https://www.anchorterminal.com/niches/workflow-automation.connect-app-accounts/index.md (~1,650 tokens)
- Slim: https://www.anchorterminal.com/niches/workflow-automation.connect-app-accounts/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/workflow-automation.connect-app-accounts/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 | 25 | 8 | 5 |

## What counts as done

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

How agents ask for it: connect my HubSpot so the flow can run; set up the Gmail credential; the client needs to connect their Salesforce

## 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.)**: 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.
- **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.
- **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.
- **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.
- **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.
- **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).
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

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

- 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.
- 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.
- 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.
- not this job: Motive Agents (Motive Technologies, Inc.): No connection API for Agents.

## What stops agents finishing

- connection needs a person at a consent screen
- connector's OAuth omits a scope its own tools need
- API-key-only apps leave keys in email
- tokens are not exported when moving platforms

## Around it

Before: workflow-automation.build-workflow. After: workflow-automation.run-workflow-as-tool, workflow-automation.unattended-sync.

## Where this comes from

Weight 8 of 100 in Workflow automation: 5 of 48 accounts (n8n forum agencies, Pipedream MCP scope gap, migration threads)

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

---

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