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

# Microsoft Teams

> Start flows from Teams messages, chats, teams, channels and members, and send and read messages, read meetings and transcripts, and manage teams and channels

Use Microsoft Teams to start a flow from a message or a change in your teams, and to work with Teams from inside a flow. This flow copies every Support message that says "urgent" to the Escalations channel. Press **Run** to watch it.

Node
Output in this run

Every trigger and node needs a Teams connection. See [Connect Microsoft 365](https://docs.noxus.ai/integrations/providers/microsoft.md) to set one up.

| Connection | Use it for | Sign in |
| - | - | - |
| **Teams** | Every trigger, and every node except the two below | OAuth, or a service principal |
| **Teams (Channels and Presence)** | Create Teams Channel and Get Teams User Presence | OAuth, or a service principal |

A service principal reads meetings, transcripts and your own chats and teams only when its connection has a **User ID or Email (UPN)**: the account to read them for.

## Triggers

Teams Message Received starts a flow when Microsoft Teams reports a new message. The other triggers check Teams every minute (Chat Joined every five minutes). Their first check only records what is already there, so chats, teams, channels and members that existed before you turned the trigger on never start a flow. Each one starts a flow once, even if it leaves and comes back. A check starts at most 25 flows; the rest start on the next checks.

What it does

## Nodes

| Node | What it does |
| - | - |
| [Send Teams Message](#send-teams-message) | Posts a message in a channel or a private chat |
| [Read Teams Messages](#read-teams-messages) | Reads the latest messages of a channel or a private chat |
| [List Teams Meetings](#list-teams-meetings) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Lists your Teams meetings between two dates |
| [Get Teams Meeting Transcript](#get-teams-meeting-transcript) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Gets the transcript of a meeting |
| [List Teams](#list-teams) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Lists the teams the connection can see |
| [List Teams Channels](#list-teams-channels) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Lists the channels of a team |
| [Get Team Members](#get-team-members) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Gets the people in a team |
| [Create Teams Channel](#create-teams-channel) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Creates a channel in a team |
| [Get Teams User Presence](#get-teams-user-presence) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Gets whether someone is available, busy or in a call |

What it does

## Troubleshooting

> [accordion] Teams access was denied
>
> For an OAuth connection, reconnect it and allow the access the node needs. Meetings and transcripts need **Read meetings & transcripts**. For a service principal, an admin must grant the Microsoft Graph permission named in the error. See [Connect Microsoft 365](https://docs.noxus.ai/integrations/providers/microsoft.md).

> [accordion] Microsoft Teams refused access to ...
>
> A trigger could not read your chats, teams or the team it watches. Reconnect Teams, or choose a connection that can read it.

> [accordion] This Teams service-principal connection has no user set
>
> Meetings, transcripts, Chat Joined and Team Joined read one account's data. Edit the connection and fill in **User ID or Email (UPN)** with that account.

> [accordion] No Teams meeting matches this join URL
>
> Use the `join_url` from List Teams Meetings, or the join link from the meeting invite.

> [accordion] Set both Meeting start and Meeting end
>
> In Get Teams Meeting Transcript, set both from List Teams Meetings, or leave both empty to get the latest occurrence.

> [accordion] This chat could not be accessed
>
> Check that the chat still exists and that the connected account is a member of it.

> [accordion] The specified Teams channel does not exist...
>
> Check the team and channel, and that the connected account can see the channel.

> [accordion] Team ... was not found
>
> The team was deleted, or the connection cannot see it. Pick the team again from the list.

> [accordion] User ... was not found
>
> Check the email address or user ID in **User**.

> [accordion] Failed to subscribe to messages in Teams: ...
>
> Teams Message Received could not start listening to the team or chat. Check the connection and the selected team and channel, then save the trigger again.

> [accordion] Microsoft Teams is busy or unavailable...
>
> A trigger could not reach Teams. This usually clears up within a few minutes, and the trigger tries again on its next check.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.