close
Skip to content

add-incoming-webhook.md

Latest commit

 

History

History
237 lines (176 loc) · 11.9 KB

add-incoming-webhook.md

File metadata and controls

237 lines (176 loc) · 11.9 KB
title Create an Incoming Webhook
description Create an Incoming Webhook to Teams app and post external requests to Teams. Remove Incoming Webhook. Sample code(C#, Node.js) to send card using Incoming Webhook.
ms.localizationpriority high
ms.topic conceptual
ms.owner hantony
ms.date 04/01/2026

Create Incoming Webhooks

[!INCLUDE deprecation-note]

An Incoming Webhook lets external applications share content in Microsoft Teams channels. The webhooks are used as tools to track and notify. The webhooks provide a unique URL to send a JSON payload with a message in card format. Cards are user interface containers that include content and actions related to a single article. You can use cards in the following capabilities:

  • Bots
  • Message extensions
  • Connectors

Note

Key features of Incoming Webhooks

The following table provides the features and description of an Incoming Webhook:

Features Description
Adaptive Cards using an Incoming Webhook Adaptive Cards can be sent through Incoming Webhooks. For more information, see Send Adaptive Cards using Incoming Webhooks.
Actionable messaging support Actionable message cards are supported in all Microsoft 365 groups including Teams. If you send messages through cards, you must use the actionable message card format. For more information, see Legacy actionable message card reference and message card playground.
Independent HTTPS messaging support Cards provide information clearly and consistently. Any tool or framework that can send HTTPS POST requests can send messages to Teams through an Incoming Webhook.
Markdown support All text fields in actionable messaging cards support basic Markdown. Don't use HTML markup in your cards. HTML is ignored and treated as plain text.
Scoped configuration An Incoming Webhook is scoped and configured at the channel level.
Secure resource definitions Messages are formatted as JSON payloads. This declarative messaging structure prevents the insertion of malicious code.

Note

  • Teams bots, message extensions, Incoming Webhook, and the Bot Framework support Adaptive Cards. Adaptive Card is an open cross-card platform framework that is used in all platforms such as Windows, Android, and iOS. Teams connectors don't support Adaptive Cards. However, it is possible to create a flow that posts Adaptive Cards to a Teams channel.
  • For more information on cards and webhooks, see Adaptive Cards and Incoming Webhooks.

Create Webhooks using Workflows

The Workflows app in Microsoft Teams enables you to create automated workflows that can receive HTTP requests through a webhook URL. When the webhook triggers, the workflow can post a message or an Adaptive Card to a Teams channel or chat.

Workflows are powered by Microsoft Power Automate and provide a flexible way to process webhook payloads before posting them to Teams.

Create an incoming webhook from a template

You can create a webhook workflow directly from a channel using a template.

  1. In Microsoft Teams, go to the team and channel where you want to receive webhook messages.
  2. Select More options (...) next to the channel.
  3. Select Workflows. :::image type="content" source="../../assets/images/connectors/add-workflows.png" alt-text="Workflows option selected in the channel menu.":::
  4. Search for and select a template such as Send webhook alerts to a channel. :::image type="content" source="../../assets/images/connectors/workflows-template-selection.png" alt-text="Select the Send webhook alerts to a channel template.":::
  5. Configure the workflow parameters. :::image type="content" source="../../assets/images/connectors/workflows-parameters.png" alt-text="Add the parameters.":::
  6. Select Save.
  7. After the workflow is created, copy the webhook link. :::image type="content" source="../../assets/images/connectors/workflows-url-copy.png" alt-text="Copy the webhook URL generated by the workflow."::: Use the webhook URL in your external application or service to send HTTP POST requests.

When a request is received, the workflow posts the configured message to the selected channel.

Create a webhook workflow from scratch

You can also create a webhook workflow manually using the Workflows app.

  1. In Microsoft Teams, select Apps. The app gallery appears.

  2. Search for and open the Workflows app. :::image type="content" source="../../assets/images/connectors/search-workflows.png" alt-text="Search for workflows.":::

  3. Select Build from scratch. :::image type="content" source="../../assets/images/connectors/workflows-build-from-scratch.png" alt-text="Build from scratch.":::

  4. Select the trigger When a Teams webhook request is received. :::image type="content" source="../../assets/images/connectors/webhook-trigger.png" alt-text="Select the trigger.":::

  5. Configure the trigger settings.

  6. Save the workflow.

Send a request to the webhook

After creating the workflow, send an HTTP POST request to the generated webhook URL.

POST <WEBHOOK_URL>
Content-Type: application/json

{
    "text": "Hello from a webhook workflow!"
}

When the request is received, the workflow processes the payload and posts the message to the configured Teams channel or chat.

When to use Workflows for webhooks

Use Workflows when you need to:

  • Receive webhook requests from external services.
  • Post messages or Adaptive Cards to Teams channels or chats.
  • Transform or process webhook payloads before posting them to Teams.
  • Integrate webhook events with other services supported by Power Automate.

Important

You can build a notification bot Teams app using Microsoft 365 Agents Toolkit (previously known as Teams Toolkit) other than an Incoming Webhook. They perform similarly but notification bot has more functionalities. For more information, see Build notification bot with JavaScript or Incoming Webhook notification sample.

You can create and send actionable messages through an Incoming Webhook or connector for Microsoft 365 Groups. For more information, see create and send messages.

Note

In Teams, select Settings > Member permissions > Allow members to create, update, and remove connectors, so that any team member can add, modify, or delete a connector.

Example

C#

Sample code reference

var adaptiveCardJson = @"{
  ""type"": ""message"",
  ""attachments"": [
    {
      ""contentType"": ""application/vnd.microsoft.card.adaptive"",
      ""content"": {
        ""type"": ""AdaptiveCard"",
        ""body"": [
          {
            ""type"": ""TextBlock"",
            ""text"": ""Message Text""
          }
        ],
        ""$schema"": ""http://adaptivecards.io/schemas/adaptive-card.json"",
        ""version"": ""1.0""
      }
    }
  ]
}";

var webhookUrl = "https://xxxxx.webhook.office.com/xxxxxxxxx";

var client = new HttpClient();
client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));

var content = new StringContent(adaptiveCardJson, System.Text.Encoding.UTF8, "application/json");
var response = await client.PostAsync(webhookUrl, content);

JavaScript

Sample code reference

var formatted_Card_Payload = {
        "type": "message",
        "attachments": [
            {
                "contentType": "application/vnd.microsoft.card.adaptive",
                "contentUrl": null,
                "content": {
                    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
                    "type": "AdaptiveCard",
                    "version": "1.2",
                    "body": [
                        {
                            "type": "TextBlock",
                            "text": "Submitted response:"+ response
                        }
                    ]
                }
            }
        ]
    }

var webhookUrl = "https://xxxxx.webhook.office.com/xxxxxxxxx";

axios.post(webhookUrl , formatted_Card_Payload )
    .then(res => {
        console.log(`statusCode: ${res.status}`)
        console.log(res)
    })
    .catch(error => {
        console.error(error)
    })

Manage your workflows

You can manage your workflows by turning them on or off, or by deleting them when no longer needed.

Turn on or turn off your workflow

Turn on or turn off a workflow at any time from the Workflows app.

  1. Open the Workflows app.

  2. Scroll down the Home page to find the Your workflows section.

  3. Next to the workflow you want to turn on or turn off, select More actions (…).

  4. From the menu, select Turn on or Turn off.

    :::image type="content" source="../../assets/images/connectors/workflows-turn-on-off.png" alt-text="Workflows-turnon-off.":::

Delete your workflow

Remove a workflow from your list at any time.

  1. Open the Workflows app.

  2. Scroll down the Home page to find the Your workflows section.

  3. Next to the workflow you want to delete, select More actions (…).

  4. Select Delete. :::image type="content" source="../../assets/images/connectors/workflow-delete.png" alt-text="Workflow-delete.":::

  5. In the confirmation window, select Delete to permanently remove the workflow.

    :::image type="content" source="../../assets/images/connectors/workflow-delete-pop-up.png" alt-text="Workflow-delete-popup.":::

Code sample

Sample name Description .NET Node.js
Incoming Webhook This sample demonstrates a Teams tab to send message cards using Incoming Webhook, showcasing the HttpPOST action for interactive cards. View View

See also