Escalate to the humans who can answer
A workflow posts the conversation into the channel that owns it — with the customer, the transcript and a link back — and the reply comes back to the thread.
Where the team already talks — and where escalations tend to get decided. Connect it once and your copilot works with channels, messages, threads, users and files 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
Copilot rides inside the inbox. With Slack connected it reads channels, messages, threads, users and files and acts on them from the same panel as the conversation — no second tab, no copying an order number across.
What a specific connection exposes is decided by Slack, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.
Once Slack 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.
The picker is the authority on which events your Slack connection publishes — these are the kinds that apps of this sort emit.
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.
The rows you name become the variables downstream steps read, so a branch can test what Slack said.
A step budget and a model tier per node — the loop stops where you told it to.
The loop can call the Slack tools you left enabled and nothing else.
A workflow posts the conversation into the channel that owns it — with the customer, the transcript and a link back — and the reply comes back to the thread.
Copilot searches history for the last time this shipping exception came up, so an agent gets the precedent rather than reopening the debate.
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
The catalogue runs to hundreds of apps and is searchable. Connect Slack from its card.
You sign in on Slack's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
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.
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.