Skip to content

Outlook Integrations

Turn your Outlook inbox into finished work.

Shared mailboxes like orders@, invoices@ and support@ are where work arrives, and where people copy it out by hand. We connect Outlook to your other systems through Microsoft Graph: read incoming mail, extract attachments, draft replies with AI, send from templates and create the record in your CRM or ERP.

Written by Roberto Postolovski, Founder & Tech LeadUpdated

Today

How it works now

The email arrives in Outlook. Then a person becomes the integration.

We've built email systems before: email, PDF-generation and template services for a US health-benefits platform serving 50,000+ employees during open enrollment.

  1. 01Someone reads every message in the shared mailbox to decide what it is.
  2. 02Attachments are downloaded and saved, renamed or re-typed into another system.
  3. 03Replies are written from scratch, or pasted from an old email that worked.
  4. 04The customer, order or ticket is updated in the CRM or ERP by hand.
  5. 05When the person who knows the mailbox is away, work waits.

The native connector

Where Outlook's standard automation stops

Microsoft documents these limits for the Office 365 Outlook connector used by Power Automate and Logic Apps, and for Microsoft Graph itself:

Sources

  • If many emails arrive at the same time, the connector's trigger can miss some of them. Microsoft notes this is rare.
  • Item attachments (emails or invites attached to an email, including bounce messages) aren't supported by the connector.
  • The trigger can run twice for one email, the first time with an empty attachments array.
  • The connector allows 300 API calls per connection every 60 seconds.
  • Microsoft Graph limits each app to 10,000 requests per 10 minutes and 4 concurrent requests per mailbox.
  • Change-notification subscriptions expire and must be renewed, and the Mail.Read.Shared permission doesn't support subscriptions on shared or delegated folders.

The automation

How we replace it

Microsoft Graph with change notifications, not mailbox polling, and least-privilege permissions scoped to the mailboxes involved.

  1. 01

    Map

    Which mailboxes, which kinds of email, and what each one should turn into.

  2. 02

    Listen

    Graph change notifications on the mailbox, with subscriptions renewed automatically and a catch-up sync for anything missed.

  3. 03

    Understand

    Each email is classified, and data is extracted from the body and attachments, including PDFs, spreadsheets and attached emails.

  4. 04

    Draft

    A reply is drafted from your templates and the email's content, and placed in Outlook for a person to check and send.

  5. 05

    Approve

    Nothing is sent and no record is created without approval until the workflow has proven itself.

  6. 06

    Monitor

    Every email handled is logged with what was done and why, and failures are reported the same day.

Typical workflows

  • Shared mailbox triage
  • Attachment extraction to ERP or storage
  • AI-drafted replies for review
  • Template-based outgoing mail
  • Email → CRM records and tasks
  • Custom Microsoft Graph work

Systems involved

  • Outlook / Exchange Online
  • Microsoft Graph
  • Shared mailboxes
  • SharePoint & OneDrive
  • Your CRM or ERP
  • Anthropic Claude / OpenAI

What stays with your team

Automation should remove the repetition, not the responsibility.

  • Sending replies until the workflow is proven
  • Emails the system can't classify with confidence
  • Anything involving payment details or contracts
  • Tone and relationship-sensitive conversations

What changes

Measured against your own baseline, not against a benchmark.

  • Shared mailboxes are sorted before anyone opens them
  • Attachments land in the right system without re-typing
  • Replies start from a good draft instead of a blank page
  • Every handled email leaves an audit trail

Questions

Common questions

Can AI draft replies to incoming emails in Outlook?
Yes. A draft can be generated from the incoming email, your templates and data from your own systems, and saved in Outlook's Drafts folder so a person reviews and sends it.
Does this work with shared mailboxes?
Yes. Using Microsoft Graph with application permissions scoped to specific mailboxes avoids several of the shared-mailbox limits of the standard Power Automate connector.
How is this different from Microsoft Copilot?
Copilot helps an individual user write and summarize. This is a workflow for a team's mailbox: it reads incoming mail, pulls out data, updates your other systems and keeps a log of what it did.
Can emails be sent automatically?
They can, but we start with drafts and human approval. Automatic sending is switched on only for the cases that have proven reliable, and stays logged.

What’s one repetitive process your team does every day?

Tell us about it. We’ll help you determine whether it can be automated, what it would take, and whether the numbers make sense.