Articles in this section

See more

Sample Teams Power Automate Workflow Webhook (Versions: 14.0+)

QuerySurge has long emphasized team communication and information-sharing in its design. As part of that emphasis, webhook support has been introduced in QuerySurge 10.0. This article describes the basic setup for Microsoft Teams webhooks using the Power Automate workflows app. 

  Important Note: Earlier versions of Teams webhooks utilized the Office 365 connectors, which Microsoft has announced the retirement of. This article discusses the Power Automate workflow feature for Teams webhooks, now recommended by Microsoft and supported by QuerySurge. 

Teams Webhooks

QuerySurge installs with four prebuilt sample Power Automate Teams webhooks, which you can use as-is, or modify for your needs:

Update: Scenario Started

Update: Scenario Ended

Results: Scenario Execution

Results: Scenario Summary

 

This article describes the webhook setup for the Teams Update: Scenario Started webhook.

 

Prerequisite: Create the Webhook

Many webhook products require some amount of setup in order for QuerySurge (or any other external system) to send in webhook messages. In Teams, the Incoming Webhook feature needs to be enabled. During the setup process, a unique URL is generated for your incoming webhook, which you'll need in order to setup your webhook in QuerySurge. For details, you'll need to consult the product documentations (for Teams, start with this article).

 

A Sample Teams Webhook

Lets review the setup for the Update: Scenario Started webhook. This is the simplest webhook message that you can send to Teams; as the name implies, this example announces on Teams that a Scenario execution has started.

  1. Edit the webhook name if you so choose

  2. Notice that the "Scenario Started" event has been pre-selected.

  3. Add an optional Description (as needed).

  4. The Request Method of POST is almost invariably the method for any webhook (QuerySurge does support a PUT option).

  5. The webhook Provider is Teams.

  6. The Endpoint URL must be entered - you'll get it from Teams when you set up your (incoming) webhook in Teams.

  7. No special HTTP Headers are required for Teams webhooks (however other webhooks may have header requirements). There is a default Content-Type header that is generally required for any webhook.

  8. The Webhook payload, as noted, is a JSON format for an adaptive card (which follows the Teams JSON syntax): 
    {
      "type": "message",
      "attachments": [
        {
          "contentType": "application/vnd.microsoft.card.adaptive",
          "content": {
            "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
            "type": "AdaptiveCard",
            "version": "1.2",
            "body": [
            {
                "type": "TextBlock",
                "text": "Scenario Ended",
                "wrap": true,
                "weight": "Bolder"
            },
            {
                "type": "TextBlock",
                "text": "${scenarioName}\n\n[${endTime}]",
                "wrap": true
            }
            ]
          }
        }
      ]
    }
    Notice there are two fields in this example denoted by dollar-signs and curly braces: ${Scenario Name} and ${Start Time}. This notation is QuerySurge-specific, and gives you access to QuerySurge values in your webhooks messages.  You can see the fields that are available by clicking on the icon at the upper right of the payload. The fields available are dependent on the QuerySurge event (a different set is available for each event) you have selected. When you choose a field off the list, it will automatically be entered into your JSON at the current insertion point.

  9. You have the option to add additional filters on an event. For example, you could limit the firing of the webhook to a specific owner (i.e. user), or in the "Scenario Ended" event, to whether the execution passed or failed.

  10. Teams webhooks offers 3 options for authentication. Each will have a unique endpoint URL layout and configuration.
        a) Anyone: Select Authentication None (Sig token is provided on the URL endpoint from teams)
           

        b) Any user in the tenant: Select Key authentication and provide Authentication Bearer token              key as specified in Microsoft's article
         

        c) Only a specific subset of users:  Select Key authentication and provide Authentication Bearer          token key as specified in Microsoft's article
           

    Note: Do not pass an authentication token header if you selected the "Anyone" authentication option. If you select the "Any user in my tenant" or "Specific users in my tenant" authentication option, you will need to pass an authentication token in requests to the When a Teams webhook request is received trigger. Refer to Microsoft's documentation for more information on these settings. 

  11. At the bottom right, there is a Save button with an arrow at its right. When you click on the arrow, a popup Test Webhook button shows, which allows you to test your webhook setup with dummy data. Error messages are reported along the bottom of the window. Once your setup is working, use the Save button to save your webhook.

  12. The Webhook message appears in Teams when your Scenario starts execution:

Related articles