Many Salesforce teams now use the Microsoft Teams service to collaborate, chat, and hang out. Gearset supports sending notifications for change monitors, continuous integration jobs, and test monitors to a Microsoft Teams channel.

Creating a Microsoft Teams incoming webhook

The first thing you need to do is generate a URL that is unique to your Microsoft Teams channel so that Gearset can send notifications to it. 

Note: This process may change when Microsoft change the Microsoft Teams user interface so you can always refer to the Microsoft Teams documentation on docs.microsoft.com.  

  1. In Microsoft Teams, choose More options (⋯) next to the channel name and then choose Connectors.
  2. Scroll through the list of Connectors to Incoming Webhook, and choose Add.
  3. Enter a name for the webhook, upload an image to associate with data from the webhook, and choose Create.
  4. Copy the webhook to the clipboard and save it. You'll need the webhook URL when configuring Gearset to send notifications to Microsoft Teams.
  5. Choose Done.

Sending updates to a Microsoft Teams channel from Gearset 

Refer to our documentation for unit testing, change monitoring, or continuous integration for instructions on how to configure those parts of Gearset. When you come to the section on configuring notifications, you can now use the Microsoft Teams webhook URL from step 4, and when the job runs you'll receive notifications from Gearset in that channel.

What if I don't get a notification even after configuring it?

Microsoft Teams can be a little confusing. A good thing to check is what the webhook URL looks like. 

It should be similar to https://outlook.office.com/webhook/{id} and that is the URL that allows you to send notifications to the channel.

It should not look like https://teams.microsoft.com/channel which is a direct link to the channel itself and isn't valid for sending notifications to.

If you have any problems configuring things, we're always here to help. You can reach us either via the in-app chat or by emailing [email protected].


 

 

Did this answer your question?