> ## Documentation Index
> Fetch the complete documentation index at: https://help.reevo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Teams Workflow Messaging

> Connect Microsoft Teams to Reevo and configure workflows that send direct messages or post to standard Teams channels.

## Overview

Reevo workflows can send Microsoft Teams messages in two ways:

| Node                           | What it does                                                            |
| :----------------------------- | :---------------------------------------------------------------------- |
| **Send Teams DM to User**      | Sends a direct message to one or more people in your Reevo workspace.   |
| **Send Teams Channel Message** | Posts a new message to a standard channel in a selected Microsoft team. |

Both nodes are generally available to customers with Microsoft Teams connected and configured. One organization-level connection supports every workflow in your Reevo workspace.

<Info>
  Workflow messaging uses the Microsoft Teams integration in **Organization settings**. It is separate from the Outlook Calendar connection used to add Teams conferencing to meetings.
</Info>

***

## Before You Start

You need:

* Organization Admin access in Reevo.
* A Microsoft work or school account in the same tenant as the people and teams you want to message.
* Permission from your Microsoft administrator to connect Reevo.
* The Reevo Teams app allowed for the intended people and teams in Microsoft Teams.

<Info>
  Only standard channels are supported. Microsoft Teams private and shared channels are not available in the channel picker and cannot receive workflow messages.
</Info>

***

## Connect Microsoft Teams

1. Open [**Settings → Integrations → Organization**](https://app.reevo.ai/settings/integrations?tab=organization).
2. Find **Microsoft Teams** under **Workspace integrations**.
3. Select **Connect**.
4. Sign in with your Microsoft work or school account and complete the Microsoft consent flow.
5. Return to Reevo and confirm that the integration shows **Connected**.

<Info>
  Only an Organization Admin can create the organization-level Microsoft Teams connection. If Microsoft blocks the connection or a later send, ask your Microsoft administrator to approve Reevo and make the Reevo Teams app available to the intended people or teams.
</Info>

***

## Send a Teams Direct Message

Use **Send Teams DM to User** when a workflow should privately notify one or more people, such as a deal owner, account manager, or approver.

### Configure the node

1. In the workflow editor, select **+** where you want to add the message.
2. Select **Send Teams DM to User**.
3. Under **Users**, select one or more people from your Reevo workspace.
4. Write a message of up to 1,000 characters. You can combine text, workflow variables, and Markdown formatting.
5. Complete the rest of the workflow and activate it.

<Note>
  Each selected Reevo user must have an email address that matches a user in your organization's Microsoft Teams directory.
</Note>

### Multiple recipients and partial delivery

Reevo sends the direct message separately to each selected person. If one recipient cannot be found or reached, the other recipients can still receive their messages.

The run history shows the overall result and the success or failure for each recipient. A run can therefore show partial success when only some messages were delivered.

***

## Send a Teams Channel Message

Use **Send Teams Channel Message** for team-visible notifications, such as a new high-value deal, an approval request, or a pipeline update.

### Configure the node

1. In the workflow editor, select **+** where you want to add the message.
2. Select **Send Teams Channel Message**.
3. Select a Microsoft team.
4. Select one of that team's standard channels.
5. Write a message of up to 1,000 characters. You can combine text, workflow variables, Markdown formatting, and user mentions.
6. Complete the rest of the workflow and activate it.

<Info>
  Select the team before selecting a channel. Reevo only lists standard channels that belong to the selected team.
</Info>

### Mention a Teams user

Use the message editor's mention control to add a person. Reevo resolves the person against your Microsoft Teams directory and sends a real Teams mention when possible.

If a person cannot be resolved, the message can still be sent without an active mention. Confirm that their account exists in the connected Microsoft Teams tenant when troubleshooting mention behavior.

***

## Use Workflow Variables and Formatting

Both nodes support static text, values from the trigger, and outputs from earlier workflow nodes. For example:

> A new opportunity for **Acme** was assigned to **Alex**.

Messages support Markdown formatting.

<Tip>
  Keep operational messages short and put the most important variable values near the beginning so recipients can understand the notification from the Teams preview.
</Tip>

***

## Build Teams Nodes with Ask Reevo

Ask Reevo can add and configure both Microsoft Teams nodes when it builds a workflow. Describe the destination and message in plain language.

For example:

> When an opportunity moves to Closed Won, send the owner a Teams DM and post a summary in the Sales channel.

For channel messages, Ask Reevo grounds the team and channel against the destinations available in your connected Microsoft tenant. For direct messages, it selects recipients from your Reevo organization.

Review unresolved recipients, teams, channels, fields, or variables before activating the workflow.

***

## Run History

| Node                           | Run details                                                                                |
| :----------------------------- | :----------------------------------------------------------------------------------------- |
| **Send Teams DM to User**      | Successful and failed message counts, plus the display name and result for each recipient. |
| **Send Teams Channel Message** | Team and channel display names, plus whether the message was sent successfully.            |

***

## Troubleshooting

Use these **6 checks** to resolve common Microsoft Teams workflow messaging problems.

### 1. Microsoft Teams is not connected

Open **Organization integrations** and connect or reconnect Microsoft Teams. Workflow fields remain unavailable while Reevo detects a missing or invalid connection.

### 2. Teams or channels do not load

Select **Try again** in the picker. If the problem continues, reconnect Microsoft Teams so the organization can grant the required directory permissions.

### 3. A direct-message recipient fails

Confirm that the selected person:

* Is still an active user in your Reevo organization.
* Has an email address in Reevo.
* Has a matching user in the connected Microsoft Teams tenant.
* Is allowed to use the Reevo Teams app under your Microsoft policies.

<Note>
  After checking the recipient, re-run the failed workflow. Other recipients from the original run may already have received their messages.
</Note>

### 4. A channel is missing

Confirm that you selected the correct team. Only standard channels appear; private and shared channels are not supported.

### 5. The selected team does not own the channel

Edit the node and select the team again, then select one of its listed channels.

### 6. Reevo cannot post because the app is unavailable

Ask your Microsoft administrator to allow or install the Reevo Teams app for the intended person or team, then re-run the workflow.

***

## Disconnect Microsoft Teams

Disconnecting the organization integration stops Reevo from sending Microsoft Teams workflow messages until the integration is reconnected.

The person who connected Microsoft Teams can open **Organization integrations**, open the Microsoft Teams integration menu, and select **Disconnect**.

<Warning>
  Disconnecting affects every active workflow that uses a Microsoft Teams messaging node in your organization.
</Warning>

***

## FAQs

<AccordionGroup>
  <Accordion title="Can a workflow send both direct messages and channel messages?">
    Yes. Add both nodes anywhere their messages should run, including on different branches of the same workflow.
  </Accordion>

  <Accordion title="Can I send to private or shared channels?">
    No. Microsoft Teams workflow messaging supports standard channels only.
  </Accordion>

  <Accordion title="Can I send a direct message to someone who is not a Reevo user?">
    No. The direct-message node selects people from your Reevo organization. Each recipient must also match a user in the connected Microsoft Teams tenant.
  </Accordion>

  <Accordion title="Can I mention someone in a direct message?">
    The direct-message node sends to the selected recipients. Inline Teams mentions are supported in channel messages, not direct messages.
  </Accordion>

  <Accordion title="Does connecting Outlook Calendar also connect workflow messaging?">
    No. Connect Microsoft Teams under Organization integrations to use the workflow messaging nodes. Outlook Calendar controls calendar and conferencing features.
  </Accordion>

  <Accordion title="What happens if one direct-message recipient fails?">
    Reevo continues with the other recipients and records a partial result. Check the run history for each recipient's result before re-running the workflow.
  </Accordion>
</AccordionGroup>

> Still have questions? [Sign in](https://app.reevo.ai) and use Ask Reevo for instant answers or to raise a support ticket.