Integrations · Messaging & email

Slack in the conversation.

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

Slack
Messaging & email
01 · COPILOT

Ask for it in plain language. It does the Slack part.

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.

  • Post a message to a channel or a person
  • Reply inside an existing thread
  • Search the workspace’s message history
  • List channels and who is in them
  • Read a thread to summarize what was decided

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.

02 · WORKFLOWS

Something happens in Slack. A workflow starts.

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.

  • A message is posted in a channel
  • The bot is mentioned

The picker is the authority on which events your Slack connection publishes — these are the kinds that apps of this sort emit.

03 · THE AI AGENT STEP

One step that decides which Slack 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 Slack 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 Slack tools you left enabled and nothing else.

What teams do with it

Two ways Slack earns its connection.

01

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.

02

The answer was already in Slack

Copilot searches history for the last time this shipping exception came up, so an agent gets the precedent rather than reopening the debate.

Setup

Connect Slack in about a minute.

  1. 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. 2

    Find Slack in Browse

    The catalogue runs to hundreds of apps and is searchable. Connect Slack from its card.

  3. 3

    Authorize with your own Slack account

    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.

  4. 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.

Slack questions.

How do I connect Slack to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for Slack. Connecting it opens Slack's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.
What can Cloodot do in Slack?
Work of this kind: post a message to a channel or a person; reply inside an existing thread; search the workspace’s message history; list channels and who is in them; read a thread to summarize what was decided. The exact list depends on what your Slack account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which Slack tools Cloodot may use?
Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Slack connection is a matter of leaving the writes off.
Can an event in Slack start a Cloodot workflow?
Yes. Events like a message is posted in a channel, the bot is mentioned appear in the workflow editor's trigger picker once Slack is connected, and the event's own fields become variables the rest of the workflow can read.
Who in my team can connect Slack?
Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Slack account that authorized it, so a messaging & email connection is only ever as broad as the account behind it.
See it on your own inbox

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.