Connect Microsoft Teams to Savant to deliver system notifications directly into your Teams channels. Once configured, Savant can route workspace and global notifications to Teams, keeping your team informed of activity without leaving their collaboration platform.
Features
This is a write-only connector. Savant delivers notifications to Microsoft Teams; it does not read data from Teams.
Write to Microsoft Teams — Savant sends notifications to a designated Microsoft Teams channel using a Teams webhook URL as the authentication endpoint.
Requirements
An active Microsoft Teams account with access to the target team and channel.
Permission to add and configure the target Teams channel.
Connection Methods
Microsoft Teams authenticates through a Microsoft Teams Channel URL.
Step 1: Open Microsoft Teams and navigate to the team and channel that should receive Savant notifications.
Step 2: Select the channel's options menu (the ⋯ next to the channel name) and choose Workflows. Choose Send Webhook Alert to Channel
Step 3: Create a new Webhook
Step 4: Copy the Webhook URL
Step 5: Within Savant
Click on Systems and Add System.
Select the Microsoft Teams connector and click Next.
Paste the Channel URL copied from Microsoft Teams into the connector configuration.
Click Test Connection to confirm Savant can reach the channel, then click Save.
To route notifications from a specific workspace, open the Admin tab, go to the workspace menu, select the target workspace, open its details, and use the notification tab to assign the Microsoft Teams connector.
Troubleshooting
Notifications not delivered — Verify the webhook URL was pasted in full and has not expired or been regenerated in Teams. A regenerated webhook invalidates the previous URL; update the connector with the new URL.
Authentication / invalid connector error — If Savant reports an expired or invalid connector, re-create the webhook in Teams and update the URL in the Savant connector configuration.
Test Connection fails — Confirm the target Teams channel still exists and that the webhook is still enabled on that channel. Deleting the channel or removing the webhook breaks the connection.
Permission errors in Teams — Adding a webhook requires sufficient rights on the team. If the option is unavailable, ask a Teams administrator to enable connectors/workflows for the channel or to create the webhook on your behalf.
Connector option not visible in Savant — Creating and managing notification connectors is admin-only. Non-admin users will not see the global notification menu or the workspace notification tab; sign in with an administrator account.
Network / IP errors — Ensure Savant's IP ranges are whitelisted on any firewall or proxy between your network and Microsoft Teams. See the IP whitelisting article linked in Requirements.
Notifications reach the wrong channel — Each webhook URL is bound to a single channel. Confirm the URL was generated on the intended channel, and create separate connectors for separate channels.
Important Notes
Microsoft Teams is a write-only notification destination. It cannot be used as a data source in Savant.
Each webhook URL targets one specific Teams channel. To deliver notifications to multiple channels, generate a webhook URL per channel and configure a connector for each.
If a webhook is regenerated or removed in Microsoft Teams, the corresponding Savant connector must be updated with the new URL, or notification delivery will stop.