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 workflows, refer to our Quick guide for workflows.

Example of a Teams expiration alert (click to enlarge):

Prerequisites

  • You must have a Manager or Administrator role to configure IT Glue workflows.

In this article, 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 with this feature.

Instructions

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.

    Microsoft_Teams_Connectors.png

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

    MS_Teams_Incoming_Webhook.png

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

    MS_Teams_New_Webhook.png

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

    MS_Teams_Copy_URL.png

  7. Click Done

Defining the trigger and filters

  1. Open IT Glue and navigate to Account > Workflows.

    Account_Sidebar_Workflows.png

  2. Click + New.
  3. Choose the trigger you want to use.
    • Documents - Triggers when a document is published or updated
    • Passwords - Triggers when a password is added or updated
    • Domain Expirations - Triggers when the specified lead time is met on a domain's expiration date
    • SSL Expirations - Triggers when the specified lead time is met on a SSL expiration date
    • Configuration Expirations - Triggers when the specified lead time is met on a configuration's (warranty) expiration date
    • Flexible Asset Expirations - Triggers when the specified lead time is met on a flexible asset's expiration date
  4. To configure the trigger:
    • Trigger Name: Enter a descriptive name for the trigger (e.g. Send license expiration alerts to Microsoft Teams). 
    • Notify At (Lead Time): Only applies to expiration-based triggers. Specify the number of days in advance that you want to be notified when an asset is nearing its expiration. For example, if you enter 10, you will receive notice 10 days in advance of the expiration date.
      • (Optional) Check the Expire sooner than the lead time and Have already expired boxes to schedule a one-time job that will notify you of existing assets that are about to expire (i.e. sooner than the specified lead time) or are already expired. So, if your lead time is 10 days, and you check these boxes, IT Glue will check whether there are any assets that are already within 10 days or less of their expiration, or that are past their expiration date.
    • Notification Failure Email: When notifications fail, an email will be sent to this email address from notifications@itglue.com.

      Example:

      MS_Teams_Configure_Trigger.png

  5. If you chose an expiration-based trigger, you can estimate how many notifications your trigger criteria will generate by clicking the Estimate How Many button.
  6. To add a filter, click the + Filter button (left side of the screen) and select your filter criteria using the drop downs. 

    Example:

    MS_Teams_Configure_Filter.png

Defining the action

  1. Next, choose the action that will be triggered.

    Webhook_Choose_Action.png

  2. To configure the action:
    • Action Name: Enter a descriptive name for the action (e.g. Notify in #general Teams channel 10 days in advance).
    • Webhook URL: Enter the Webhook URL copied from 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 Teams channel.

      Example:

      MS_Teams_JSON_Payload.png

      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.

  3. Click Next.
  4. Click the Test Action button to test the action. If the notification goes through, the connection has been established.
  5. Put the workflow in an On status and then click Finish to save all your changes.

Your team will now start receiving notifications to Teams within the next 24 hours. Note that notifications based on document or password triggers will be sent in real time.

From there, you can use a system of emoji reactions to let team members claim, investigate, and mark problems as resolved, or have conversations about specific notifications.

Further reading:

 

Note: You can download either of the following icons to upload to Teams. This will help your team visually verify where the messages originated:

gluebot-slack-512x512.pngitglue-slack-512x512.png

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