Webhooks and connectors
Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams. Webhooks are user-defined HTTP callback that notifies users about any action that has taken place in the Teams channel. It's a way for an app to get real-time data. Connectors allow users to subscribe to receive notifications and messages from your web services. They expose an HTTPS endpoint for your service to post messages in the form of cards.
Webhooks help Teams to integrate with external apps. With Outgoing Webhooks, you can send text messages from a channel to a web service. After configuring the Outgoing Webhooks, users can @mention Outgoing Webhook and send a message to a web service. The service responds within 10 seconds to the message with a text or a card.
Outgoing Webhooks are configured on a per team basis and cannot be included as part of a normal Teams app.
Connectors allow users to subscribe to receive notifications and messages from the web services. They expose the HTTPS endpoint for the service to post messages to Teams channels, typically in the form of cards.
Incoming Webhooks help in posting messages from apps to Teams. If Incoming Webhooks are enabled for a team in any channel, it exposes the HTTPS endpoint, that accepts correctly formatted JSON and inserts the messages to that channel. For example, you can create an Incoming Webhook in your DevOps channel, configure your build, and simultaneously deploy and monitor services to send alerts.
Notification bot or Incoming Webhook
Before you start to learn how to build Incoming Webhooks, you may also want to know that you can build a notification bot using Teams Toolkit. Notification bots can enable more customizable experience to meet different business scenarios.
Learn more about the differences between a notification bot and Incoming Webhook so that you can choose the right solutions for your scenarios:
|Notification bot||Incoming Webhook|
|What is it?||A Teams app||A Teams feature|
|Suitable scenarios||• Receive regular notifications and messages periodically, for example, receive daily notification of team tasks.
• Receive notifications and messages based on real events. For example, once teammates upload files, you receive notifications.
|Communicate with external apps and receive notifications and messages from other apps.|
|Scope configuration||• Teams channel
• Group chat
• Personal chat
|Message process||A notification bot works as a Teams application. You can define your business logic to process data and show data in a customized format.||Webhook is a Teams feature rather than a Teams application, so it only receives and shows data without processing.|
|Retrieve Teams context||Notification bot can retrieve Teams context such as the channel or user information, messages, etc.||No|
|Send Adaptive Card||Yes||Yes|
|Send a welcome message||Yes||No|
|Trigger supported||All triggers are supported. If you use Teams Toolkit, you can quickly get a template project with the following triggers:
• Time trigger hosted on Azure functions.
• Restify HTTP trigger hosted on Azure app service.
• HTTP trigger hosted on Azure Functions.
|All triggers are supported.|
|Building Tools||• Teams Toolkit Overview for Visual Studio Code
• Teams Toolkit overview for Visual Studio
• TeamsFx Library
• TeamsFx SDK
|No tools are required.|
|Cloud resource required||Azure Bot Framework||No resources are required.|
Connectors for Microsoft 365 Groups
Connectors for Microsoft 365 Groups allow you to create a custom configuration page for your Incoming Webhook and package them as part of a Teams app. You send messages primarily using connector cards for Microsoft 365 Groups and can add a limited set of card actions to them. For example, a weather connector that allows users to select a location and any time of the day, to receive updates about tomorrow's weather. They're configured at channel level but are installed at team level.
You can distribute the connector for Microsoft 365 Groups Teams app to our AppStore.
Create and send messages
Actionable messages allow users to take action without leaving their email client, increasing user engagement. With Microsoft 365 and Incoming Webhooks, you can send messages by posting a JSON payload to the webhook URL.
Submit and view feedback for