Slack Integration

Connect Slack once and anyone in a mapped channel can mention @CloudThinker to ask about your cloud, then keep talking in the thread. The same connection delivers notifications, such as alerts and code review summaries, to the channels you choose.

Prerequisites

A CloudThinker organization Owner or Admin. Other roles can view the Slack page but can’t connect or change it.
A Team, Scale, or Enterprise plan. On the Free plan the Slack card shows Requires Team plan or above and an Upgrade Plan button. See pricing.
Permission to install apps in your Slack workspace. If your Slack workspace uses app approval, a Slack Workspace Owner or app manager has to approve CloudThinker.
CloudThinker hosted at app.cloudthinker.io. A self-hosted install shows Not available on self-host on the Slack card.

Each Slack workspace can connect to one CloudThinker organization.

Connect Slack

A channel the bot is in but that has no mapping still runs requests, in the organization Owner’s default workspace and with that workspace’s connections. There’s no setting to make unmapped channels refuse requests. Check the mapping right after every invite, and remove the bot from channels that shouldn’t reach your infrastructure.

Open the Slack integration

Go to Admin Settings → Integrations, find the Slack card, and click Go to configure.

Click Connect with Slack

Slack opens its authorization screen. Pick the Slack workspace and click Allow.Connecting replaces any Slack workspace this organization connected before.Success state: you return to the Slack page with a Slack connected successfully message, and the Setup card shows your Slack workspace name and Team ID under Connect to Slack.

Invite the bot to a channel

In Slack, open the channel your team will use and run:

/invite @CloudThinker

CloudThinker maps the channel to a CloudThinker workspace automatically. It picks the organization Owner’s default workspace, or the oldest workspace if the Owner has none.Success state: the channel appears under Configure channel-workspace mappings on the Slack page.

Check which workspace each channel uses

Under Configure channel-workspace mappings, open the Select workspace menu on each channel row and pick the workspace whose connections that channel should use.Success state: a Channel mapping updated message appears and the row shows the new workspace.

Send a test message

In the channel, mention the bot with a question:

@CloudThinker What drove our cloud spend up last week?

Success state: CloudThinker replies in a thread under your message. Reply in that thread to follow up. You don’t need to mention the bot again.

Who requests run as

Slack users in a regular channel all run as one account, while a war room matches the sender by email and runs as that user or refuses — In a regular channel every request runs as one account; only war rooms match the sender by email.

CloudThinker doesn’t match Slack users to CloudThinker accounts in regular channels, and Slack has no account linking. Unlike Google Chat, which runs each request as the sender, every request runs as one account: whoever created the mapped workspace, or the organization Owner for a workspace the organization owns, with that account’s access. A Slack user needs no CloudThinker account to ask a question. CloudThinker records the Slack sender’s name and Slack user ID on each message in the conversation. Incident war rooms are the exception. A war room is a Slack channel that Resolve creates for one incident (see Add a Slack war room). There, CloudThinker matches the sender by email and runs the request as that CloudThinker user, or refuses it if there’s no match with access. War-room questions also appear in Admin Settings → Audit Logs under the sender’s name. Because of this, treat channel membership as access. Map a channel only to a workspace that everyone in the channel may use.

Ask CloudThinker in Slack

Every request starts with @CloudThinker. After that, you write the same requests you’d type in the web app. Talk to agents in plain language. The full pattern is:

@agent #connection your request

@agent (optional) — leave it out and CloudThinker answers, or mention one of your workspace’s custom agents.
#connection (optional) — the connection to use, such as your AWS account or a Kubernetes cluster.
/ (optional) — run a skill or a command.
Your request — what you need, in your own words. Add any context inline.

See Commands for the full list.

@CloudThinker Which EC2 instances ran under 10% CPU for the last 14 days?
@CloudThinker Summarize open critical security findings for production
@CloudThinker Why did checkout latency spike at 14:00 UTC today?

What to expect in the thread:

You see	What it means
is typing…	CloudThinker is working on the request
A reply in the thread	The answer. The full conversation also appears in the CloudThinker web app
Permission required to use a tool, with View in CloudThinker	The request needs an action that your Approvals setup holds for a person. You can’t approve in Slack: open the link and an allowed approver approves or rejects it in the web app

CloudThinker answers mentions in channels and replies in its own threads. To start a new topic, mention @CloudThinker in a new message. Private channels work the same way once you invite the bot. CloudThinker doesn’t answer direct messages: its Home tab in Slack tells you to mention it in a channel. CloudThinker reads the text of your message only, so paste the content you want it to read instead of attaching a file.

Send notifications to Slack

Slack is also a destination for workspace notifications. Each CloudThinker workspace has its own Slack channel, so switch to the right workspace in the workspace switcher at the top of the sidebar first.

Open notification settings

On the Slack page, under Configure notifications, click Go to notification settings. You can also go to More → Workspace settings → Notifications.

Pick a default channel for the workspace

Under Delivery channels, find the Slack card (it reads Pick a channel until one is set). Click its settings icon (Change Slack channel), then search for and select a channel under Slack Notification Channel. You can pick any public channel, or a private channel the bot was invited to.

Override per notification type (optional)

Under What to notify me about, turn on the Slack cell for an event, then click the → #channel chip next to it to send that event to a different channel. The Alerts and Keepers rows also have a severity picker. See Notifications for the full list of types.Success state: the next matching event posts in the chosen channel.

Code review notifications

When Review finishes a pull request or merge request on a connected repository, CloudThinker can post a summary to Slack:

A count of findings by severity
Up to 5 unresolved findings, each with its title, file path, and line number
How many earlier findings are now resolved
A View Review button that opens the review in CloudThinker
No issues found when the review is clean

Choose the channel and severity threshold for reviews in Notifications.

Security and permissions

Question	Answer
Which messages it acts on	Messages that mention `@CloudThinker`, and replies in threads CloudThinker started. When you call it into an existing thread, it can read that thread for context
What CloudThinker stores	Your requests and its replies, saved as a conversation in the mapped workspace, plus the link between each Slack thread and that conversation

CloudThinker requests these Slack bot scopes:

Scope	Why
`app_mentions:read`	Receive messages that mention `@CloudThinker`
`channels:history`, `groups:history`	Read replies in its threads, and the thread you call it into, in public and private channels
`channels:read`, `groups:read`	List channels for the mapping table and the notification picker
`channels:manage`	Create incident war-room channels and invite responders
`chat:write`	Post replies and notifications
`chat:write.public`	Post notifications in a public channel without joining it first
`files:write`	Post files CloudThinker produces, such as reports, in the thread
`users:read`	Show the sender’s display name on the conversation
`users:read.email`	Match a war-room sender to a CloudThinker account by email
`im:read`, `im:history`, `im:write`, `mpim:read`, `mpim:history`	Requested by the app. CloudThinker doesn’t answer direct or group messages today

Manage the connection

Task	How
Move a channel to another workspace	Change Select workspace on its row in Configure channel-workspace mappings
Stop routing a channel	In Slack, run `/remove @CloudThinker` in the channel. That also deletes the row. Don’t remove only the row: the bot stays in the channel, and the channel falls back to the default workspace
Reconnect for new permissions	If the page shows Slack needs one more permission, click Reconnect Slack. Existing messages and notification channels keep working
Disconnect	Click Disconnect from Slack at the bottom of the Slack page. CloudThinker uninstalls the app from Slack and deletes every channel mapping, the links between Slack threads and conversations, and the Slack notification settings. Reconnecting starts from scratch

Troubleshooting

Slack authorization not completed

Slack denied or cancelled the authorization, or your Slack workspace requires admin approval. Ask a Slack Workspace Owner or app manager to approve CloudThinker in Slack’s app management, then click Connect with Slack again.

Slack workspace already connected

That Slack workspace is already connected to another CloudThinker organization. A Slack workspace can connect to only one. Disconnect it from the other organization first, or use a different Slack workspace.

Not authorized

Only organization Owners and Admins can configure Slack. Ask one of them to connect it, or to change your organization role.

The bot doesn't reply

Check that the bot is in the channel (/invite @CloudThinker) and that you mentioned it in a new message. A message without the mention gets a reply only inside a thread CloudThinker already started.If CloudThinker replies No workspace is configured for this channel, it couldn’t find a workspace to use: the organization has no active workspace, or the channel’s row points to a workspace outside this organization. Open the Slack page and set a workspace on the channel’s row.

The answer uses the wrong account or cluster

The channel is mapped to a different workspace than you expected. Check its row under Configure channel-workspace mappings and change Select workspace.

You don't have access to this incident in CloudThinker

Incident war-room channels only run requests from people who have a CloudThinker account in that workspace with access to incidents and chat. CloudThinker matches you by email, so use the same email in Slack and CloudThinker, or ask a workspace Admin for access.

Notifications don't arrive

Check that a Slack Notification Channel is set for the workspace, that the notification type is on, and that the event meets the severity threshold. For a private channel, invite the bot first.

Next steps

Commands and prompt syntax

Write sharper requests and save the ones your team repeats

Notifications

Choose which events reach Slack and at what severity

Approvals

Decide which actions need a person before CloudThinker runs them

Microsoft Teams

Set up the same workflow in Teams

Start here

Learn the basics

Help

Work where you are

Prerequisites

Connect Slack

Who requests run as

Ask CloudThinker in Slack

Send notifications to Slack

Code review notifications

Security and permissions

Manage the connection

Troubleshooting

Next steps

Commands and prompt syntax

Notifications

Approvals

Microsoft Teams

​Prerequisites

​Connect Slack

​Who requests run as

​Ask CloudThinker in Slack

​Send notifications to Slack

​Code review notifications

​Security and permissions

​Manage the connection

​Troubleshooting

​Next steps

Commands and prompt syntax

Notifications

Approvals

Microsoft Teams

Prerequisites

Connect Slack

Who requests run as

Ask CloudThinker in Slack

Send notifications to Slack

Code review notifications

Security and permissions

Manage the connection

Troubleshooting

Next steps