How to Connect Outlook and Teams to Send Email Notifications Automatically | Steps to Post Incoming Mail

You want messages from business partners to be visible not only in your own inbox but also in a Teams channel. For people who use Microsoft 365, this article explains how to post incoming Outlook mail to Teams.

The short answer

In a Samurai App workflow, use Outlook's "New Outlook Message" as the trigger and follow it with two "Run external service" steps. The first fetches the email, and the second posts to a Teams channel.

  • What you can do: post email filtered by sender, recipient, words in the subject, whether it has attachments, and importance to a channel you choose
  • What you cannot do: receive the body at the moment of the trigger. The body is read in the fetch step
  • What you cannot do: post with a personal Microsoft account. A work or school account is required
  • What you cannot do: watch shared mailboxes or folders accessed by delegation

What you can and cannot do

The incoming-mail event does not include the body. What reliably arrives with the Outlook trigger is the email's id. outlook_message, which contains the subject and so on, is sometimes missing, and the official guidance is to fetch it with OUTLOOK_GET_MESSAGE when it is absent. A step fails if a field you insert has not arrived, so this article puts the fetch step in from the start.

Unlike Gmail, there is no polling delay. The Outlook trigger is webhook-based and does not have the up-to-15-minute delay that Gmail does. We could not find a figure in the official documentation for how many seconds it takes to arrive.

Filters are separate fields for each Outlook property. Rather than a search expression like Gmail's, they are split into from_email, to_email (the To recipients only; Cc and Bcc are not covered), subject_contains, has_attachments, importance, and folder_id. folder_id defaults to the inbox, and you cannot specify shared mailboxes or folders accessed by delegation. With has_attachments, images embedded in the body also count as attachments.

Teams Incoming Webhooks have changed. The older Incoming Webhooks that used Office 365 connectors were retired in May 2026, and you now create them with the Teams Workflows app. For Workflows webhooks, the official documentation lists Adaptive Cards and MessageCards as the supported formats, while also showing an example that sends only text. Samurai App's "Send to notification destination" sends a format centered on text, and we have not checked it against a real Teams instance. So this article posts through the Teams connector instead.

Only send what people will read. Microsoft treats using Teams as a place to dump logs as a violation of its terms of use. Do not forward every email; always filter.

What you need

  • An Outlook account, and a work or school Microsoft account that is in Teams
  • Outlook and Microsoft Teams connected under "Connectors" in Samurai App
  • The team_id of the team to post in and the channel_id of the channel
  • Permission to attach a service integration to a workflow (manager or higher)

Steps

1. Connect Outlook and Teams

On the Connectors screen, "Add" Outlook and Microsoft Teams, and connect each with your own account. Adding connectors is an admin and manager operation. If your organization's settings block the connection, check with your Microsoft 365 administrator.

2. Look up the team and channel IDs

Posting takes IDs, not team names. You can look them up by asking in chat, "List my Teams teams and the channel IDs in the [name] team." A channel ID looks like 19:…@thread.tacv2.

3. Build the workflow

Create a draft with "New" and add an input named event of type "Group of fields" under "Workflow inputs."

Add "Run external service" from "Connect," choose OUTLOOK_GET_MESSAGE, and put the following in message_id:

{{input.event.id}}

Add another "Run external service," choose MICROSOFT_TEAMS_TEAMS_POST_CHANNEL_MESSAGE, and fill in the values.

Name Value
team_id The team ID from step 2
channel_id The channel ID from step 2
content The fetched email's subject and sender

Press "/" in the content field to choose the subject and other fields from the previous step's "Output fields." If they are not among the suggestions, run it once, open the fetch step's output under "Recent runs," and check the names of the fields that came back.

4. Publish

"Save," then press "Publish version N" on the "Versions" tab. The trigger does not start runs until you publish.

5. Add the trigger and filter it

Press "Add service integration" on the "Triggers" tab.

  1. Under "Which service to watch," choose your Outlook connection
  2. Under "What triggers it," choose "New Outlook Message"
  3. Fill in from_email, subject_contains, and so on under "Filter"

A service integration costs about 0.5 yen per event received.

6. Try it

Send an email that matches the conditions and check that it is posted to Teams. Run results are kept under "Recent runs" on the workflow's "Runs" tab.

When it does not work

  • The fetch step fails with a 404: the official documentation says a 404 can happen for deleted mail, mail in another mailbox, or an ID in an old format. Check for rules that immediately move or delete the email
  • The post step fails for lack of permission: posting requires a work or school account. Personal Microsoft accounts are not supported. Also check that the account used for the Teams connection is a member of the team you are posting to
  • It is refused by an administrator setting: if an administrator has set this operation to "Confirm every time" or "Forbidden," unattended runs are refused
  • It does not trigger, or it runs more often than expected: subject_contains is case-insensitive but does distinguish leading and trailing spaces. to_email looks only at To, so it does not match mail that arrives as Cc

Frequently asked questions

Can I also show the email body in Teams?

You can insert the body from the fetch step into content. However, everyone in the channel will see it, so for an inbox where inquiry bodies contain personal information, you may decide to post only the subject.

Whose name is the post made under?

It posts with the account used for the Teams connection. By default it runs with the account of the person who created the trigger, and you can fix it with "Lend to this workflow" under the step's "Credentials used to run."

Can I also send to a chat or to an individual?

For chats there is a separate operation, MICROSOFT_TEAMS_TEAMS_POST_CHAT_MESSAGE. This article covers only posting to a channel.

Related guides

Sources

Related featureConnect business tools to AI over MCPSamurai App connects your business tools to AI over MCP. Operate accounting and HR SaaS from chat within each person's own permissions, call the agent from Slack or Teams, and use it from outside AI clients over MCP.

More automation examples

See every way to connect and automate Microsoft Teams

Back to How-to articles

Everyday work comes together, connects, and becomes the company's strength.

Contact usOpen Samurai App

See the demoContact us