Connected apps

Connected apps are how cmdk acts in the software your company already uses. A connection is an authorised account. Once it exists, its actions appear as tools, and its events can trigger automations.

Connecting an app

On the Tools page press Add connection, pick the app, and sign in to it in the window that opens. When you return, the app is listed with the number of actions it offers. Apps that need an API key instead of a login can be connected from an automation's Connections section, which asks for the credentials.

Connections belong to the workspace, not to the person who connected them. Every agent and automation in the workspace can be allowed to use them; nobody has to connect the same account twice.

Choosing actions

The dropdown on an app's group header on the Tools page sets its approval mode; see Tools. On an agent, choose which connections it may act in under Connections. On an automation, do the same on its Settings tab: pick the connections, allow or block individual actions per connection, and switch which account is used when the workspace has more than one for the same app.

Using connected apps

• In chat, the agent picks the right action from the description: "email the summary to the customer" sends with Gmail if Gmail is connected.
• In automations, the builder adds the actions to the plan when you mention the app in your brief.
• As triggers, a connected app can start a run on an event, such as a new email matching a filter or a new row in a sheet. The builder sets this up when your brief asks for it.

Reconnecting

A connected app offers Reconnect in its connection section, for when a login has expired or you want to switch the account.

Searching the catalogue

The app pickers search across every available app, connected or not: type a name and the list narrows as you type.