Microsoft Teams Integration - Basic Webhook Setup Guide

This guide covers the step-by-step process of integrating ChangeBreeze with Microsoft Teams. You will learn how to generate a webhook within the ChangeBreeze platform and configure Microsoft Teams Workflows to automatically post notification cards to your selected channel.

1. Firstly in Microsoft teams open the Apps section, search for Workflows and install it.
   
2. Open the Workflows App, select New Flow in the top right of the application and then select Create from blank again in the top right.
3. From here, add the trigger as "When a Teams webhook request is received". You can use the search function to find this.
   
4. You will be presented with the webhook trigger settings, set "Who can trigger the flow?" to Anyone, then select New Step.
5. The operation we will be using is "Post card in a chat or channel".
   
6. Use the following settings:
   Post as: Flow bot
   Post in: Channel
   Team: Select the team you would like to post in
   Channel: Select the Channel the card will be posted in
   Adaptive Card: Click in the text box, in the window that pops up select the Expression tab, copy the following in to the fx text box.
   triggerBody()?['attachments'][0]?['content']
   Then press OK > Save.
   
   Example:
   
7. Re expand the "When a Teams webhook request is received" trigger to obtain the webhook URL. "HTTP POST URL". Save this somewere for later.
8. Now over to changebreeze.com sign in and navigate to Settings > Notifications. Select Add Webhook. In this case I am using an Org Wide Webhook but this will work using  Org or Company only webhooks as well.
9. Give it a name, paste in the webhook URL, give it a description and select the change type. In my example I will use Emergency Changes Only. Click Create Webhook.
   
10. Since this is a global notification, I will now test it by creating an emergency change. Noting if Org or Company only webhooks are used they will need to be selected in the communication plan section.
    
    Note: Teams cards are only sent when the change is fully approved, emergency bypassed, started, progress updates, completed or rolled back.
11. The basic implementation is completed.
    
    The above image shows the card successfully being sent to Microsoft Teams in the Emergency Changes channel. If the emails used for stakeholders match users within teams they will also be notified.

While this guide covers the fundamental steps for receiving a webhook in Teams, it really only scratches the surface of what is possible. By leveraging the rich data sent from ChangeBreeze alongside the logic-building power of Teams Workflows, you can transform simple notifications into robust business processes. For instance, you could use the EventV4 connector to automatically sync changes to a centralized SharePoint calendar or implement conditional logic to alert specific stakeholders.