Skip to main content
Use Slack to start and continue CloudThinker conversations, route work to specialists, and receive configured notifications.

​
Prerequisites

  • A CloudThinker organization owner or administrator on a messaging-eligible plan (Team and above).
  • A Slack Workspace Owner or app manager when the workspace requires App Approval. This provider approval is separate from CloudThinker organization access.

​
Setup

1

Start with a CloudThinker administrator

Sign in as a CloudThinker organization owner or administrator on a messaging-eligible plan.
2

Navigate to integrations

Go to Admin Settings → Integrations and find Slack
3

Connect with Slack

Click Add to Slack and authorize via Slack’s OAuth flow.If your workspace has App Approval enabled, a Slack Workspace Owner or app manager must approve CloudThinker. This approval does not replace CloudThinker organization authorization.
4

Install the app

Select which Slack workspace to install CloudThinker into and confirm the OAuth scopes. The app appears in your workspace’s app directory.
5

Map channels to workspaces

Map Slack channels to CloudThinker workspaces. The mapping controls where ordinary Slack messages run.
A message from an unmapped Slack channel runs in the organization’s oldest workspace — including its connections. Map every channel the bot can see, and remove the bot from channels that should not run prompts.
6

Configure notifications

Configure destinations for each notification type in the notification matrix — the grid that maps each event type to destinations — such as cost alerts, security findings, and incident updates.
7

Test

Start a conversation with @CloudThinker @alex show AWS costs. The @CloudThinker mention starts a CloudThinker thread. Reply in that thread without mentioning @CloudThinker again.

​
Syntax

In Slack, use @CloudThinker to start a CloudThinker thread. Reply in an existing CloudThinker thread without mentioning the bot again. To route a request to a specialist, add the agent’s alias after the bot mention. Talk to agents in plain language. The full pattern is:
  • @agent — who does the work: @alex (cloud), @oliver (security), @tony (database), @kai (Kubernetes), @anna (coordination).
  • #tool (optional) — the output you want: #dashboard, #report, #visualize, #recommend, #alert.
  • Your request — what you need, in your own words. Add any context inline.
See the CloudThinker Language reference for the full syntax.

​
Examples

Quick queries — bot mention, then agent alias, then your question:
Tool tags and multiple agents work the same as in the web app:

​
Alerts

Configure alert notification destinations in the notification matrix. A #alert request and a plain request can raise alerts, but neither can send an alert to a specific channel from within the prompt — destinations come from the notification matrix.

​
Code review notifications

When an AI code review completes on a connected repository, CloudThinker can send a summary notification to your Slack channels. These notifications use Slack’s rich Block Kit formatting with:
  • Severity indicators — color-coded emoji for each severity level (🔴 Critical, 🟠 High, 🟡 Medium, 🟢 Low)
  • Severity breakdown — count of findings by severity
  • Finding details — up to 5 unresolved findings with title, file path, and line number
  • Resolved count — number of previously identified findings that have been resolved
  • View Review button — direct link to the review dashboard
  • Clean pass — when no issues are found, a simple “No issues found” message
Configure code review destinations and severity thresholds in the notification matrix at Notifications → Review / Pipeline Monitoring. See Notifications Center for details.

​
Troubleshooting

  • Check if CloudThinker app is added to the channel
  • Start a new conversation with @CloudThinker and use a literal alias such as @alex for specialist routing
  • Reply in an existing CloudThinker thread without repeating @CloudThinker
  • Confirm agents are configured in the CloudThinker console
  • Check the Slack workspace’s App Approval status
  • Check alert configuration in CloudThinker Settings
  • Verify the Slack destination in the notification matrix
  • Ensure the bot has permission to post in the target channel
  • “Missing required scopes” — The app may have been installed without all required OAuth scopes. Remove the app from the workspace and reinstall it from CloudThinker’s Integrations page.
  • Connection appears successful but bot doesn’t respond — This can happen if the OAuth flow did not complete fully. Try removing and reinstalling the app.
  • “not_allowed_token_type” or scope errors — Your Slack workspace may have App Approval enabled. Ask your Workspace Owner or app manager to approve CloudThinker in Slack’s admin dashboard under Manage Apps.
  • For any other permission errors, confirm the channel-to-workspace mapping and try removing and re-adding the app to the channel.
A CloudThinker organization owner or administrator on a messaging-eligible plan starts the setup. If Slack App Approval is enabled, a Slack Workspace Owner or app manager completes the provider approval. These can be different people.
  1. Sign in to CloudThinker as an organization owner or administrator on a messaging-eligible plan
  2. Go to Admin Settings → Integrations → Slack
  3. Click Add to Slack and complete the Slack OAuth flow
  4. Approve the app in Slack’s Manage Apps dashboard
After configuration, start a new CloudThinker thread with @CloudThinker. Replies in that thread do not need another bot mention.

​
Permissions

​
Slack OAuth permissions

Slack App Approval governs whether the Slack installation can proceed. It is separate from the CloudThinker organization owner or administrator and messaging-eligible plan required to start setup.

​
CloudThinker permissions

The channel mapping selects the workspace a message runs in, and ordinary channel messages run there regardless of the sender’s CloudThinker role. Incident war-room channels — dedicated channels opened for an incident — are stricter: a message there runs only when the Slack sender is linked to an active CloudThinker user with permission to view incidents and use chat; otherwise CloudThinker replies that access was denied.

CloudThinker Language

Complete syntax reference for all commands

Microsoft Teams Integration

Set up CloudThinker in Microsoft Teams