The Slack integration enables Cora to post updates, alerts, and insights directly into your team's Slack channels. Once connected, Cora can deliver lifecycle event notifications, customer health updates, and other automated messages where your team already collaborates.

Integration Type: OAuth 2.0, Organization-Level
​Setup Time: 2-3 minutes
​Required Role: Slack Workspace Admin (to approve the app) + Cora Organization Administrator

The Cora Slack app requests a pre-approved set of permissions during installation — no manual scope configuration is needed. These permissions allow Cora to read and post messages in channels it has been added to, identify workspace members, and respond to @mentions and slash commands.

Note: Cora only reads messages in channels it has been explicitly added to. It does not have access to channels or direct messages it has not been invited to.

Enterprise Grid: If your organization uses Slack Enterprise Grid with multiple workspaces, make sure you select the correct workspace from the dropdown during the authorization step. Cora is installed per workspace, not org-wide — installing it on the wrong workspace means it won’t have access to your team’s channels.

Once the app is installed in your workspace, you need to invite Cora to each channel where it should be active. Type the following in the channel’s message box:

/invite @Cora

You can also click the channel name → Integrations → Add an App → select Cora.

If another company you share a Slack Connect channel with also uses Cora, their Cora bot may become visible across your workspace. This means you could see two Cora bots when inviting — not just in the shared channel, but in any channel in your workspace.

When inviting Cora, pay attention to the workspace shown next to each bot in the invite dialog. Always pick the one associated with your workspace. Inviting the wrong instance means messages won’t route to your Cora account.

If you’re unsure which bot is yours, check with your Slack workspace admin.

Cora must be invited to every channel where you want it active — including public, private, and Slack Connect channels. For private and Slack Connect channels in particular, the bot cannot join on its own and must be manually invited.

Tip: Start with a dedicated channel (e.g., #cora-alerts or #customer-updates) to test the integration before rolling it out more broadly.

For external channels (Slack Connect or shared channels with customers), Cora automatically detects the channel and links it to the matching customer account based on the email domains of the channel’s members.

Once linked, Cora can:

Note: Each customer account can only be linked to one external channel at a time. If the account is already linked to a different channel, the auto-link will be skipped. You can update the linked channel manually in Cora’s settings.

For internal channels, auto-linking does not apply. You’ll need to set the internal channel manually in the customer organization’s settings.

Cora distinguishes between two types of channels for each customer account:

If you want Cora active in both contexts, invite the bot to both channels. For external channels, Cora handles the linking automatically. For internal channels, set the channel in the organization’s settings after inviting the bot.

Bot not responding in a channel

Confirm that Cora was the bot you invited, not a different Slack app. If another app’s bot was added instead, Cora will not receive any events from that channel. Remove the wrong bot and invite Cora.

Invited the wrong Cora bot

If another company you share a Slack Connect channel with also uses Cora, their bot can appear across your workspace — not just in the shared channel. You may have accidentally invited their instance instead of yours. Remove it and re-invite, making sure to select the Cora bot associated with your workspace. Look for your workspace name or logo next to the bot in the invite dialog.

Channel not auto-linked to a customer account

Auto-linking only applies to external channels. If an external channel wasn’t linked, the customer account may already be linked to a different channel, or the channel members’ email domains didn’t match a known customer in Cora. You can manually set the channel ID in the customer organization’s settings.

"Cannot invite" error

Check that the channel’s permissions allow adding apps and integrations. For customer-created Slack Connect channels, ask the customer to adjust their channel permissions to allow app invitations.

Messages not being tracked

Cora can only read and track messages from channels where it is a member. Ensure the bot has been invited to the channel. If it was removed at some point, re-invite it with /invite @Cora.