Setting up Microsoft Teams webhook notifications

For partners subscribed to Select or Enterprise plans.

This article will walk you through the steps for configuring IT Glue and Microsoft Teams to send webhook notifications to a Microsoft Teams channel when specific events occur.

For an introduction to IT Glue notifications, make sure you read Setting up notifications


  • You must have a Manager or Administrator role to set up notifications.


Configuring Microsoft Teams

  1. In Microsoft Teams, select a team and a channel for that team (the channel you want notifications sent to).
  2. Click the three small dots on the right side of the highlighted channel name.
  3. From the More Options menu, click Connectors.


  4. Scroll through the list and at the Incoming Webhook connector, click Configure.


  5. Give the webhook a name and a custom icon, and click Create.


  6. Next, copy the webhook URL. You will need it to configure IT Glue.


  7. Click Done.

Defining the trigger

  1. Open IT Glue and navigate to Account > Notifications.
  2. Click on + New to open the Create Notification screen.
  3. In the Trigger section, add the following details: 
    • Name: Enter a descriptive name for the trigger (e.g. Windows Teams 60 day domain expiration alert).
    • Trigger: Select the trigger you want to use. 
    • Lead time: This field only applies to expiration triggers. Enter the number of days in advance you want to receive notice. For example, if you enter 60, you will receive notice 60 days in advance of the expiration date.
      • Already expired: Check this box if you don't want any lead time (you want to receive notice on the expiration date).
      • Enroll assets that already meet this criteria: Check this box if you want to also receive notices on anything that has gone past the lead time. So, if your lead time is 5 days, and you enable this option, IT Glue will check whether there are any assets that are within 5 days or less of their expiration.
    • Admin email: This email address will be alerted if notices fail.



  4. Check the Active box.
    • You can leave this box unchecked to make changes without sending incomplete notifications (and also to disable notifications without deleting them).
  5. Click Save Trigger.

Defining the action 

In this section, we will refer to the JSON API, which is basically a universal connector for data on the internet. JSON API is a specification for how a client should request that resources be fetched or modified, and how a server should respond to those requests. You don't have to know anything beyond that to begin experimenting.

  1. In the Actions section, enter the following details:
    • Name: Enter a descriptive name for the action (e.g. Notify about domain expirations 60 days in advance).
    • Dispatch: Choose Webhook.
    • Webhook URL: Enter the Webhook URL copied from Windows Teams.
    • JSON Payload: Enter a key/value pair. The value you associate with the text key is the message that will be posted to your Window Teams channel. 



      This key/value pair includes variables that will pull values from the asset that’s triggering the notification. The available variables are listed at the bottom of the screen where you input this information.

  2. Click Save Action
  3. Click the Send test button to test the action. If the notification goes through, the connection has been established.

If the notification is active, your team will start to receive notifications to Windows Teams within the next 24 hours. Note that notifications based on document or password triggers will be sent in real time.




Further reading:

Was this article helpful?
0 out of 0 found this helpful