Skip to content

Connect Your Apps

How do I make Support helper use the right app account? Create a connection through Controller AI’s credential form or provider authorization. Confirm the account, then bind its ID to the intended node or action. Enter secrets in the secure form, never in assistant chat. A link or card is not a completed connection.

In the app: open Connections, then Add connection on an empty page or Add Connection in the header when accounts exist. Search for the app and complete its form or provider authorization.

With an assistant: for a new action, discover its exact integration/action pair below, authorize it, then follow Add agent tools to attach it. For workflow repair, find the node first. To replace an agent action’s account, find your owned agent. Substitute your agent’s name if you did not build Support helper. Search with agent_list:

{ "search": "Support helper", "ownership": "mine" }

Select one exact displayed-name match and note its data.agents[].id as <agentId>. Search matches substrings, so if names are duplicated, have the owner choose the ID.

Now list its tools with agent_tool_list:

{ "agentId": "<agentId>" }

Note the intended action’s data.tools[].id as <toolId> and nodeSlug as <nodeSlug>. Use that exact integration for the replacement.

For first-time setup, search for the action with integration_action_list:

{ "query": "Send a Slack message" }

Select the intended data.items[] action, keeping its exact nodeSlug as <nodeSlug> and key for attachment. Display names alone do not identify the integration.

Now list that integration’s accounts with connection_list:

{ "integration": "<nodeSlug>" }

Reuse the intended ACTIVE account if listed. Only when none is suitable, get an authorization link with connection_connect_url:

{ "nodeSlug": "<nodeSlug>" }

It returns url in its result data without waiting. Share data.url with the user. Links are single-use and expire after 30 minutes. If authorization does not finish, list again before authorizing again, and reuse the link only while it is unused and unexpired.

An assistant in Controller AI’s hosted builder posts a connect card into the build chat instead. An existing active connection returns connected: true without a card.

List the accounts again with connection_list and the same integration.

Compare the IDs before and after. Use the intended data.items[].id as <connectionId>. Display names in the assistant tools do not prove provider identity. Have the user confirm their selection, and inspect Linked account in Connections when present. The list excludes system connections.

Statuses are ACTIVE, MISSING, and ERROR. ACTIVE is stored eligibility, not a provider health check. Bind an ACTIVE connection with the exact slug. The assistant tools can save an inactive connection on an action, but runtime rejects it.

In the app: open Agents → Support helper → Edit → Tools. Hover the action and choose the pencil (Edit). Select Connection → Continue → Save changes, then the agent page’s Save changes. The dialog only stages your edit.

Rebinding an action already in the published version redirects subsequent Live calls immediately, without publication. Draft-only actions have no Live callers. Shared users use the agent owner’s connection.

With an assistant, rebind the tool with agent_tool_update, passing the IDs as strings, then call agent_tool_list again:

{ "agentId": "<agentId>", "toolId": "<toolId>", "connectionId": "<connectionId>" }

Verify the tool’s saved connectionId. Test against a designated Slack test channel, because tests perform real provider actions. Successful calls and provider-reported failures are billable, so inspect provider state before retrying an uncertain write.

In the app: an active workflow opens read-only in Live, so switch to Dev first. Open Workflows → Support desk → Dev → intended flow → intended action node → Connection and select the replacement account.

With an assistant: every workflow-scoped call carries an explicit workflowId. Start with workflow_list:

{}

Note the intended data.items[].id as <workflowId>. Then list that workflow’s flows with flow_list:

{ "workflowId": "<workflowId>" }

Note the intended data.items[].id as <flowId>. Then read the flow with flow_get to get its nodes.

{ "workflowId": "<workflowId>", "flowId": "<flowId>" }

Note the intended data.nodes[].id as <nodeId> and its nodeSlug as <nodeSlug>. If the node needs another account, complete authorization above using that slug, then resume with the confirmed <connectionId>.

Set the connection with node_connection_set:

{ "workflowId": "<workflowId>", "nodeId": "<nodeId>", "connection": "<connectionId>" }

Read it back with node_get and node_prop_list, each called with { "workflowId": "<workflowId>", "nodeId": "<nodeId>" }. Rebinding resets fields whose choices come from the app, such as channels or folders, and clears the dynamic field catalog. Reload, reselect destinations, and inspect all fields, because the available field set can change.

This changes development. Configure and verify the node, test its affected path, then publish the workflow to replace its Live binding.

In the app: hover the connection card, choose the pencil (Edit connection name), and press Enter to save. Grouped accounts offer Set as default.

With an assistant, rename and set default with connection_update, then call connection_list with integration again:

{ "connectionId": "<connectionId>", "displayName": "Support workspace", "isDefault": true }

Check the saved name and default. The first connection becomes the default. The app preselects defaults for new compatible nodes, triggers, and actions. Setting one clears the others for that integration. Existing bindings never retarget, and deleting the default promotes no replacement.

Check dependencies in development and Live, then replace and verify bindings, publishing repaired workflows first. The map includes workflow and direct-action connection IDs, but omits Chat in Slack, so inspect those settings separately.

Deletion removes Controller AI authorization immediately, Live included, leaving stale IDs in nodes and tools. It does not revoke provider-side access. Revoke that separately when intended. Deleting a native Slack connection closes open approval episodes and attempts to post “Approval closed — Slack was disconnected.”

In the app: hover the connection card, choose the trash icon (Delete connection), then confirm Delete.

With an assistant, delete with connection_delete, then verify with connection_list:

{ "connectionId": "<connectionId>" }

Confirm the ID is absent and inspect affected callers.