Slackbot in the conversation.
Slackbot gives agents workspace-wide read access to a Slack workspace on behalf of the installing user - search messages and files, browse channel and thread history, and look up users and channels…. Connect it once and your copilot works in it directly without leaving the thread — and your workflows can act on it while the customer is still typing.
No credit card required · 7-day free trial
Ask for it in plain language. It does the Slackbot part.
Copilot rides inside the inbox. With Slackbot connected it works there from the same panel as the conversation — no second tab, no copying an order number across.
- End a call
- Find users
- Find channels
- Create channel
- List all users
- Fetch team info
What a specific connection exposes is decided by Slackbot, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.
Something happens in Slackbot. A workflow starts.
Once Slackbot is connected, its events show up in the workflow editor's trigger picker, and the fields the event carries become variables every later step can read — so the message you send is written from what actually happened.
- New Channel Created Trigger
- Channel Message Received
- Direct Message Received
- Message Reaction Added
The picker is the authority on which events your Slackbot connection publishes — these are the kinds that apps of this sort emit.
One step that decides which Slackbot tools to call.
A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.
You declare the output
The rows you name become the variables downstream steps read, so a branch can test what Slackbot said.
You cap the effort
A step budget and a model tier per node — the loop stops where you told it to.
Only what you switched on
The loop can call the Slackbot tools you left enabled and nothing else.
Connect Slackbot in about a minute.
- 1
Open Settings → Apps
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
- 2
Find Slackbot in Browse
The catalogue runs to hundreds of apps and is searchable. Connect Slackbot from its card.
- 3
Authorize with your own Slackbot account
You sign in on Slackbot's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
- 4
Choose the tools it may call
Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.
Slackbot questions.
How do I connect Slackbot to Cloodot?
What can Cloodot do in Slackbot?
Can I limit which Slackbot tools Cloodot may use?
Can an event in Slackbot start a Cloodot workflow?
Who in my team can connect Slackbot?
Rarely just one app.
GmailThe mailbox most business email still starts and ends in.SlackWhere the team already talks — and where escalations tend to get decided.
Microsoft OutlookMicrosoft's mail and calendar client, and the default in most corporate environments.
Microsoft TeamsThe internal chat and meeting hub for organizations standardized on Microsoft 365.
DiscordWhere a lot of consumer and developer communities actually live.
WhatsAppThe messaging app most of the world already has open, and for many businesses the only channel customers actually use.Try the whole thing, today.
Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.