A connection is a saved app account that MindCloud can use to run actions.
Your MindCloud API Key authenticates your request to MindCloud. The connectionId selects the connected app account behind that request. MindCloud stores the provider credentials, refreshes them when the app supports refresh, and uses them only for the app actions you call.
Create a connection once for an app account, then reuse its connectionId across that app's actions.
| Piece | What it does |
|---|---|
| App | The provider you want to use, such as Slack, HubSpot, or Linear. |
| Connection | The saved account and provider credentials for that app. |
connectionId | The ID you pass to the Universal API action request. |
| Action | The operation MindCloud runs with the selected connection. |
Connections are app-specific. A Slack connection cannot run HubSpot actions, and a HubSpot connection cannot run Slack actions.
Apps use different authentication methods, but the Universal API request shape stays the same.
| Type | How it works |
|---|---|
| OAuth | You sign in with the provider. MindCloud stores the resulting tokens and refreshes them when supported. |
| API key | You paste a key or token from the provider into the connection form. |
| Custom | The app needs a provider-specific set of fields, such as a workspace, tenant, domain, region, or signed credential bundle. |
The action request still uses connectionId. You do not send provider access tokens, API keys, or custom credential fields with Universal API calls.
In Gravity, connections are managed from the workflow builder and the Connections area in MindCloud.
Workflow steps use a connection for the app they run. If a step has no connection, MindCloud prompts you to create one. If one valid connection exists for that app, MindCloud can use it automatically. If multiple connections exist, you can choose the one that should run that step.
Workflows can also choose connections by environment. That lets one workflow use different app accounts for different environments without changing the action shape.
In Cirra, connections are part of the conversation.
You can ask Cirra to use an app before you have connected it. Cirra checks the available connections, asks you to connect or reconnect when needed, and then continues the work after the connection is ready.
Cirra can also use company connections. These are shared at the organization level and can be assigned to roles so teams can use approved app accounts without each person creating their own.
