Microsoft Teams
Chat messages and workspace collaboration.
What it does
Posts and reads messages in Teams. Where a business lives in Teams, this is how an agent reaches people where they already are rather than by email they will not read.
What you need
An account with Microsoft Teams that you are entitled to authorise, and a moment in a browser. You do not need an API key: connecting sends you to Microsoft Teams's own sign-in and consent screen, and what comes back is an authorisation rather than a password. RAiN never sees your password, and the authorisation is held by our integration provider on our instructions — see the Integrations & Connected Accounts notice for what that means.
Connecting it
Connections belong to one project. A system built for one client never acts on another client's account, and a package handed to a business runs on theirs — so the same integration is connected again, separately, for each project that needs it.
- Open the project and stay on the Visual Editor tab.
- Open the Tools & Integrations rail on the right.
- Find Microsoft Teams and press Connect.
- Authorise in the window that opens, then come back. The rail will show it as connected.
The consent link is good for about twenty minutes. If you leave it and come back tomorrow, press Connect again rather than reusing the old tab.
To stop it, press Disconnect. That ends this project's access immediately. You can also revoke it from Microsoft Teams's own security settings, which works even if you never open RAiN again.
What an agent can do with it
71 actions are available once connected, 18 of which delete things and are marked where they appear. They appear in the tool list for this project only — a project that has not connected Microsoft Teams is never offered them.
| Action | What it does |
|---|---|
microsoft_teams_add_chat_member |
Add chat member |
microsoft_teams_add_member_to_channel |
Add member to channel |
microsoft_teams_add_team_member |
Add member to team |
microsoft_teams_add_team_members_bulk |
Add team members (bulk) |
microsoft_teams_archive_team |
Archive Teams team |
microsoft_teams_archive_channel |
Archive channel ⚠️ deletes things |
microsoft_teams_archive_group_team_channel |
Archive team channel |
microsoft_teams_clone_team |
Clone Team |
microsoft_teams_create_call_operation |
Create Call Operation |
microsoft_teams_teams_create_chat |
Create Chat |
microsoft_teams_create_team |
Create Team |
microsoft_teams_create_team_from_group |
Create Team From Group |
microsoft_teams_create_meeting |
Create online meeting |
microsoft_teams_create_open_shift |
Create open shifts |
| … | and 57 more, all listed in the rail |
Tick the ones an agent may use, or choose one in an Action step to run it exactly as written with no model involved.
A worked example
A logistics firm's exceptions channel receives a Teams message whenever a delivery misses its window, naming the order and the driver, so the duty manager sees it in seconds.
When it goes wrong
Eighteen of its actions are destructive — more than any other integration here. Be deliberate about which ones an agent may call.
See also
- Integrations & Connected Accounts — who holds the authorisation
- Action steps — running one action exactly as written
- Sequences — how steps fit together

