Skip to main content
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. Every trigger and node needs a Teams connection. See Connect Microsoft 365 to set one up. 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.

​
Nodes

​
Troubleshooting

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.
A trigger could not read your chats, teams or the team it watches. Reconnect Teams, or choose a connection that can read it.
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.
Use the join_url from List Teams Meetings, or the join link from the meeting invite.
In Get Teams Meeting Transcript, set both from List Teams Meetings, or leave both empty to get the latest occurrence.
Check that the chat still exists and that the connected account is a member of it.
Check the team and channel, and that the connected account can see the channel.
The team was deleted, or the connection cannot see it. Pick the team again from the list.
Check the email address or user ID in User.
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.
A trigger could not reach Teams. This usually clears up within a few minutes, and the trigger tries again on its next check.