Integrations · Messaging & email

Microsoft Outlook in the conversation.

Microsoft's mail and calendar client, and the default in most corporate environments. Connect it once and your copilot works with messages, folders, contacts, calendar events and attachments 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 Outlook
Messaging & email
01 · COPILOT

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

Copilot rides inside the inbox. With Microsoft Outlook connected it reads messages, folders, contacts, calendar events and attachments and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

  • Search a mailbox by sender, subject or folder
  • Read a message thread and its attachments
  • Draft or send a mail from the connected account
  • Move a message between folders
  • Read the calendar attached to the account

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

02 · WORKFLOWS

Something happens in Microsoft Outlook. A workflow starts.

Once Microsoft Outlook 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 arrives
  • A calendar event is created

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

03 · THE AI AGENT STEP

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

What teams do with it

Two ways Microsoft Outlook earns its connection.

01

Corporate email, one inbox

The Outlook mailbox your enterprise customers write to joins the same tray as WhatsApp and webchat, threaded by the customer rather than the protocol.

02

Draft, don’t send

Copilot writes the reply into Outlook as a draft so a person still presses send — useful where a mail from that address carries weight.

Setup

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

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

  3. 3

    Authorize with your own Microsoft Outlook account

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

How do I connect Microsoft Outlook to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for Microsoft Outlook. Connecting it opens Microsoft Outlook'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 Outlook?
Work of this kind: search a mailbox by sender, subject or folder; read a message thread and its attachments; draft or send a mail from the connected account; move a message between folders; read the calendar attached to the account. The exact list depends on what your Microsoft Outlook account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which Microsoft Outlook 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 Outlook connection is a matter of leaving the writes off.
Can an event in Microsoft Outlook start a Cloodot workflow?
Yes. Events like a message arrives, a calendar event is created appear in the workflow editor's trigger picker once Microsoft Outlook is connected, and the event's own fields become variables the rest of the workflow can read.
Who in my team can connect Microsoft Outlook?
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 Outlook 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.