Skip to main content
Transform your Slack workspace into a cloud operations command center. Interact with CloudThinker agents, receive alerts, and run operations without leaving Slack.
AgenticOps vs ChatOps: AgenticOps is the conversational approach to cloud operations — the broader paradigm of talking to AI agents in natural language. ChatOps is how you do AgenticOps inside Slack and Teams. The same @agent #tool syntax works identically in the CloudThinker web app and chat.

​
The problem with context switching

When an alert fires, engineers context-switch through 5+ tools: acknowledge in PagerDuty → open AWS console → check CloudWatch → pull up kubectl → open Datadog. By the time they have a full picture, 20 minutes have passed and the team is asking for updates in Slack — the one place everyone already is. Even routine operations require context switching: checking costs means opening Cost Explorer, checking security findings means opening Security Hub, checking Kubernetes means opening Lens or running kubectl commands.

​
How SlackOps is different

SlackOps works because it meets engineers where they already are — and because it provides the full intelligence of CloudThinker agents, not just notifications.

​
Setup

By default, any Slack workspace member can install apps. If your workspace has App Approval enabled, a Workspace Owner or app manager must approve CloudThinker before it can be installed.
1

Navigate to Integrations

Go to Admin Settings → Integrations and find Slack
2

Connect with Slack

Click Add to Slack and authorize via Slack’s OAuth flow.
If your workspace has App Approval enabled, CloudThinker must be approved by a Workspace Owner or app manager before you can complete this step. If the app hasn’t been approved yet, you’ll be prompted to submit a request.
3

Install the App

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

Map Channels to Workspaces

Map your Slack channels to CloudThinker workspaces so agents know which cloud accounts to operate on
5

Configure Notifications

Optionally select channels for each notification type (cost alerts, security findings, incident updates)
6

Test

Try @CloudThinker alex show AWS costs in a channel to verify the connection

​
Syntax

In Slack, prefix all commands with @CloudThinker:
All CloudThinker Language syntax works in Slack—just add the @CloudThinker prefix.

​
Examples

​
Quick queries

​
With tools

​
Multi-agent

​
Alerts

Configure agents to send alerts to Slack channels:

​
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 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 Code Review button — direct link to the review dashboard
  • Clean pass — when no issues are found, a simple “No issues found” message
Configure which Slack channel receives code review notifications and set severity thresholds in Settings > Notifications > Code Review / Pipeline Monitoring. See Notifications Center for details.

​
Channel patterns

​
Troubleshooting

  • Check if CloudThinker app is added to the channel
  • Verify you’re using @CloudThinker agent syntax (not just agent)
  • Confirm agents are configured in the CloudThinker console
  • Check Slack workspace admin consent status
  • Check alert configuration in CloudThinker Settings
  • Verify Slack channel notification settings
  • Ensure the bot has permission to post in the target channel
  • Test with /cloudthinker alerts test
  • “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, check workspace permissions in CloudThinker, or try removing and re-adding the app to the channel.
If your workspace requires app approval, here’s what to share with your Workspace Owner or app manager:
  1. Sign in to CloudThinker (they need a CloudThinker account with admin access to the organization)
  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
This is a one-time setup. Once approved, any workspace member can interact with CloudThinker by mentioning @CloudThinker in channels where the app has been added.

​
Permissions

​
Slack OAuth permissions

By default, any workspace member can install the CloudThinker Slack app. If your workspace has App Approval enabled, a Workspace Owner or app manager must approve CloudThinker before members can install it. This approval is a one-time operation — once approved, no further admin actions are required.

​
CloudThinker permissions

Within Slack, users can only access agents and cloud connections that their CloudThinker account permits. CloudThinker workspace roles apply the same way as they do in the web console.

CloudThinker Language

Complete syntax reference for all commands

Microsoft Teams Integration

Set up CloudThinker in Microsoft Teams