> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/automate/connected-apps/generic-webhook/ms-teams-webhook-example.md).

# MS Teams Webhook Example

To integrate groundcover with MS Teams, follow the steps below. Note that you’ll need at least a **Business** subscription of MS Teams to be able to create workflows.

1. **Create a webhook workflow for your dedicated Teams channel** Go to Relevant Team -> Specific Channel -> "Workflows", and create a webhook workflow
2. Normally you would select "Send webhook alerts to a channel" as your designated workflow
3. **The webhook workflow is associated a URL** which is used to trigger the MS Teams integration on groundcover - make sure to copy this URL
4. **Set Up the Webhook in groundcover**
   * Head out to **Integrations → Destinations** to create a new [Generic Webhook](/automate/connected-apps/generic-webhook.md)
   * Start by giving your Webhook integration a name. This name will be used to connect your notification from the monitor directly or through a [Notification Route](/automate/monitors/notification-routes.md).
   * Set the `Webhook URL` to the url you copied from field (3)
   * Keep the HTTP method as `POST`
5. Skip the other sections and open `Custom Payload`. Use the following example as your payload. Note that this is only an example and can be modified to fit your needs

```json
{
  "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": "Firing: {{ summary }}",
            "weight": "bolder",
            "size": "large",
            "wrap": true
          },
          {
            "type": "TextBlock",
            "text": "[See monitor]({{urls.monitor}})",
            "wrap": true
          },
          {
            "type": "TextBlock",
            "text": "[Investigate Issue]({{urls.issue}})",
            "wrap": true
          },          
          {
            "type": "TextBlock",
            "text": "[Silence]({{urls.silence}})",
            "wrap": true
          },          
          {
            "type": "TextBlock",
            "text": "{{ description }}",
            "wrap": true
          }
        ]
      }
    }
  ]
}
```

You may now test your integration or just click the `Add` button


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/automate/connected-apps/generic-webhook/ms-teams-webhook-example.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.