Post external requests to Teams with incoming webhooks
What are incoming webhooks in Teams?
Incoming webhooks are special type of Connector in Teams that provide a simple way for an external app to share content in team channels and are often used as tracking and notification tools. Teams provides a unique URL to which you send a JSON payload with the message that you want to POST, typically in a card format. Cards are user-interface (UI) containers that contain content and actions related to a single topic and are a way to present message data in a consistent way. Teams uses cards within three capabilities:
- Messaging extensions
Incoming webhook key features
|Scoped Configuration||Incoming webhooks are scoped and configured at the channel level (e.g., outgoing webhooks are scoped and configured at the team level).|
|Secure resource definitions||Messages are formatted as JSON payloads. This declarative messaging structure prevents the injection of malicious code as there is no code execution on the client.|
|Actionable messaging support||If you choose to send messages via cards, you must use the actionable message card format. Actionable message cards are supported in all Office 365 groups including Teams. Here are links to the Legacy actionable message card reference and the Message card playground.|
|Independent HTTPS messaging support||Cards are a great way to present information in a clear and consistent way. Any tool or framework that can send HTTPS POST requests can send messages to Teams via 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.|
Teams bots, messaging extensions, and the Bot Framework support Adaptive Cards, an open cross-card platform framework. Teams connectors do not currently support Adaptive Cards. However, it is possible to create a flow that posts adaptive cards to a Teams channel.
Add an incoming webhook to a Teams channel
If your team's Settings => Member permissions => Allow members to create, update, and remove connectors is selected, any team member can add, modify, or delete a connector.
- Navigate to the channel where you want to add the webhook and select (•••) More Options from the top navigation bar.
- Choose Connectors from the drop-down menu and search for Incoming Webhook.
- Select the Configure button, provide a name, and, optionally, upload an image avatar for your webhook.
- The dialog window will present a unique URL that will map to the channel. Make sure that you copy and save the URL—you will need to provide it to the outside service.
- Select the Done button. The webhook will be available in the team channel.
Remove an incoming webhook from a Teams channel
- Navigate to the channel where the webhook was added and select (•••) More Options from the top navigation bar.
- Choose Connectors from the drop-down menu.
- On the left, under Manage, choose Configured.
- Select the number Configured to see a list of your current connectors.
- Select Manage next to the connector that you want to delete.
- Select the Remove button and you will be presented with a Remove Configuration dialog box.
- Optionally, complete the dialog box fields and checkboxes prior to selecting the Remove button. The webhook will be deleted from the team channel.
You have three options for distributing your incoming webhook:
- Set up an incoming webhook directly for your team.
- Add a configuration page and wrap your incoming webhook in a O365 Connector
- Package and publish your Connector as part of your AppSource submission.