Alta has a native Microsoft Teams integration that lets you push notifications into any Teams channel as part of a Workflow — for example, ping a sales channel the moment a prospect replies, or notify a CS channel when a meeting is booked. Authentication is handled via Microsoft OAuth, so no API keys or webhooks are required.
Who this is for
Any Alta admin who wants Alta to post messages into a Microsoft Teams channel as part of a Workflow run — sales leaders, CS managers, RevOps, or anyone who already routes alerts to Teams.
Before you start
You need a Microsoft 365 account that is a member of the team(s) and channel(s) you want Alta to post into. Alta uses Microsoft Graph and can only see teams you have joined.
Your Microsoft tenant must allow third-party app consent. If your IT team restricts OAuth consent, you may need a Microsoft 365 admin to approve Alta the first time.
You should have at least one Workflow (or a campaign with Workflows enabled) where you want to add the Teams step.
Step 1 — Connect Microsoft Teams to Alta
In Alta, open Settings → Integrations.
Find Microsoft Teams in the integrations list. The card description reads "Send Alta notifications to Microsoft Teams channels."
Click Connect. You will be redirected to
login.microsoftonline.comto sign in.Sign in with the Microsoft 365 account that has access to the team(s) you want Alta to post into.
Review the permission prompt and click Accept. Alta requests the following scopes:
Team.ReadBasic.All— to list the teams you belong to in the action dropdown.Channel.ReadBasic.All— to list the channels inside the team you select.ChannelMessage.Send— to post the message itself.User.Read,email,openid,offline_access— to identify the connected account and keep the token refreshed.
You will land back on the Alta integrations page. The Microsoft Teams card now shows Connected as [email protected]. You can now send notifications to Microsoft Teams channels via Workflows.
Step 2 — Add a Send Message step in a Workflow
Open the Workflow you want to edit (or create a new one).
Click + to add a step and pick Microsoft Teams from the integration picker.
Choose the Send Message action. The description reads "Send a message to a Microsoft Teams channel."
Fill in the three fields:
Team — a dropdown of every team your connected account has joined. If you don't see a team here, you are not a member of it; join the team in Microsoft Teams and reopen the dropdown.
Channel — a dropdown of channels inside the selected team. This field stays disabled with the placeholder "Select a team first" until you pick a Team.
Message — the text of the message. You can mix plain text with Alta variables from upstream steps (for example, prospect name, campaign, reply snippet) using the variable picker.
Click Save, then run a test event through the Workflow to confirm the message lands in the right channel.
Tips and common pitfalls
Only joined teams appear. Alta reads from
/me/joinedTeamson Microsoft Graph. Private teams you have not joined, and shared channels you are not a direct member of, will not show up. Join them in Teams first.The Channel dropdown is blocked until a Team is picked. If it reads "Select a team first," go back and choose a team — the channel list refreshes off the team selection.
"Connect your Microsoft account first" placeholder. If either dropdown shows this, the OAuth connection has been removed or revoked. Reconnect from Settings → Integrations.
Message body supports HTML. Alta posts the message with
contentType: html, so basic HTML (links, bold, line breaks via<br>) will render in Teams. Plain text works fine too.One channel per step. The action posts to a single channel. To fan out to multiple channels, add one Send Message step per channel.
Retries and failures. By default, the step fails closed: Continue on failure and Retry on failure are both off. If you want Alta to keep the Workflow running even when Teams returns an error, flip Continue on failure on in the step's error-handling settings.
Tokens refresh automatically. Alta stores a refresh token (via the
offline_accessscope), so you should not need to reconnect unless your Microsoft admin revokes Alta's consent or you change tenants.Admin consent in restricted tenants. If sign-in fails with a "needs admin approval" error, ask a Microsoft 365 global admin to grant tenant-wide consent for Alta, then retry the connection.
Related
How to Schedule a Dashboard or Metric Delivery in Alta — push recurring metrics to Slack or email.
How to Invite Teammates and Manage Teams in Alta — note that "Teams" inside Alta refers to user groups, not Microsoft Teams channels.