Integrations · Messaging & email

Microsoft Teams in the conversation.

The internal chat and meeting hub for organizations standardized on Microsoft 365. Connect it once and your copilot works with teams, channels, chats, messages and members 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

Microsoft Teams
Messaging & email
01 · COPILOT

Ask for it in plain language. It does the Microsoft Teams part.

Copilot rides inside the inbox. With Microsoft Teams connected it reads teams, channels, chats, messages and members 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 chat
  • Reply in a channel thread
  • List teams, channels and members
  • Read recent messages in a channel

What a specific connection exposes is decided by Microsoft Teams, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.

02 · WORKFLOWS

Something happens in Microsoft Teams. A workflow starts.

Once Microsoft Teams 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 picker is the authority on which events your Microsoft Teams connection publishes — these are the kinds that apps of this sort emit.

03 · THE AI AGENT STEP

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

What teams do with it

Two ways Microsoft Teams earns its connection.

01

Escalations reach the department

A workflow posts to the Teams channel that owns the issue, with the customer and the thread, so the answer comes from the people who have it.

02

One notification, not four

Only the conversations matching your rule reach Teams — the rest stay in the inbox where they belong.

Setup

Connect Microsoft Teams 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 Microsoft Teams in Browse

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

  3. 3

    Authorize with your own Microsoft Teams account

    You sign in on Microsoft Teams'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.

Microsoft Teams questions.

How do I connect Microsoft Teams to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for Microsoft Teams. Connecting it opens Microsoft Teams'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 Microsoft Teams?
Work of this kind: post a message to a channel or a chat; reply in a channel thread; list teams, channels and members; read recent messages in a channel. The exact list depends on what your Microsoft Teams account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which Microsoft Teams 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 Microsoft Teams connection is a matter of leaving the writes off.
Can an event in Microsoft Teams start a Cloodot workflow?
Yes. Events like a message is posted in a channel appear in the workflow editor's trigger picker once Microsoft Teams is connected, and the event's own fields become variables the rest of the workflow can read.
Who in my team can connect Microsoft Teams?
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 Microsoft Teams 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.