Authorise the app connections a workflow needs
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
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 13
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.
| Listing | Why |
|---|---|
| Activepieces API + MCP C 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. source |
| Microsoft Copilot Studio MCP D 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. source |
| Gumloop C 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. source |
| Kognitos C 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. source |
| Make API + MCP B 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. source |
| n8n API + MCP D 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). source |
| Node-RED B 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. source |
| Paragon ActionKit + MCP D 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. source |
| Pipedream API + MCP BB 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. source |
| Prismatic C 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. source |
| Tray.ai API + MCP C 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. source |
| Windmill API + MCP D 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. source |
| Workato API + MCP C 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. source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Microsoft Power Automate C 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. source |
Doesn't do this job 4
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Bind AI F 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. source |
| Kestra C 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. source |
| Cooper (Mandl) F Cooper AI Tech, Inc. | Apps are connected by a person clicking connect in Cooper; no connection API or hosted link for a workflow. source |
| Motive Agents F Motive Technologies, Inc. | No connection API for Agents. source |
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)
The same as data: /api/v1/use-cases/workflow-automation.connect-app-accounts.json, or the MCP tool get_use_case with id workflow-automation.connect-app-accounts. Other jobs in this category: /api/v1/niches?category=workflow-automation.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.