Webhook is a Teams feature rather than a Teams application, so it only receives and shows data without processing. You can define your business logic to process data and show data in a customized format. For example, once teammates upload files, you receive notifications.Ĭommunicate with external apps and receive notifications and messages from other apps.Ī notification bot works as a Teams application. Receive notifications and messages based on real events.Receive regular notifications and messages periodically, for example, receive daily notification of team tasks.Learn more about the differences between a notification bot and Incoming Webhook so that you can choose the right solutions for your scenarios: Notification bots can enable more customizable experience to meet different business scenarios. Notification bot or Incoming Webhookīefore 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. For example, you can create an Incoming Webhook in your DevOps channel, configure your build, and simultaneously deploy and monitor services to send alerts. 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. Incoming Webhooks help in posting messages from apps to Teams. They expose the HTTPS endpoint for the service to post messages to Teams channels, typically in the form of cards. ConnectorsĬonnectors allow users to subscribe to receive notifications and messages from the web services. Outgoing Webhooks are configured on a per team basis and cannot be included as part of a normal Teams app.

Slack channel webhook