Recently, Microsoft announced it will be retiring its Office 365 connectors within Microsoft Teams. Starting August 15, 2024, all new creations must be built using the Workflows app in Microsoft Teams. Existing connectors within all clouds will continue to work until December 2025; however, using connectors beyond December 31, 2024 will require additional action by the user.
Connectors, or webhooks, are essential to everyday workflows because they direct content and updates into a Teams channel, preventing users from needing to go to a third-party service for updates on alerts or notifications. We understand that many Tines customers have such webhooks set up in their stories that allow them to send messages from Tines to Teams.
What can Tines builders do?
For builders that are currently sending messages from Tines to Teams via a webhook, you will need to set up a Microsoft Teams credential that communicates with the channel directly. From there, builders must update the action within their Tines story accordingly.
Follow our Microsoft Teams Authentication Guide for step-by-step instructions on creating a Microsoft Teams application with delegated permissions tied to a user or service account. If your organization requires a more custom Microsoft Teams credential, follow our Microsoft Graph Authentication Guide for steps to enable your preferred custom scopes.
Alternatively, Tines has many Teams templates available to pull into a story. As a starting template, our recommendation is to use “Send an adaptive cards message in a chat.” You can find this template by either searching through the Microsoft Teams templates or searching for the template within the storyboard command palette via Cmd+K
. A chat ID is required, which will point to the individual or channel you wish to receive updates.
NOTE: if you are sending communications to Tines from Microsoft Teams today, no action is required.