> 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/slack-webhook.md).

# Slack Webhook

{% hint style="info" %}
This capability is only available to BYOC deployments. Check out our [pricing page](https://www.groundcover.com/pricing) for more information about subscription plans and the available deployment modes.
{% endhint %}

### Setting Up a Slack Webhook

To get a Slack webhook URL:

1. Go to <https://my.slack.com/services/new/incoming-webhook>
2. Select the channel for notifications
3. Click **Add Incoming Webhook Integration**
4. Copy the generated webhook URL

For more details on Slack setup options, see Slack Integration.

### Configuring Slack Webhook in groundcover

1. In groundcover, go to **Integrations → Destinations**.
2. Click on 'Slack Webhook'.

<figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2FmmXKV7JbCFoC17f9H4IY%2Fimage.png?alt=media&amp;token=d55ad83c-c6cf-44d2-8bf0-4e0f88335f79" alt=""><figcaption></figcaption></figure>

3. Select a name and paste your webhook URL.

<figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2F9XlYhrEyNzI4rYwm5pJG%2Fimage.png?alt=media&amp;token=75f4c4a6-22a4-482e-a56a-2b21c744c4f7" alt="" width="375"><figcaption></figcaption></figure>

4. **Test the connection** (Optional) - sends a test notification to verify the webhook.
5. **Save**

### Slack Message Payload

groundcover sends messages to Slack using the following format:

```json
{
  "blocks": [
    {
      "type": "header",
      "text": {
        "type": "plain_text",
        "text": ":rotating_light: {{ summary }}"
      }
    },
    {
      "type": "section",
      "fields": [
        { "type": "mrkdwn", "text": "*Status:*\n{{ status }}" },
        { "type": "mrkdwn", "text": "*Severity:*\n{{ severity }}" },
        { "type": "mrkdwn", "text": "*Monitor:*\n{{ monitor_name }}" },
        { "type": "mrkdwn", "text": "*Value:*\n{{ value }}" }
      ]
    },
    {
      "type": "section",
      "text": {
        "type": "mrkdwn",
        "text": "{{ description }}"
      }
    },
    {
      "type": "section",
      "fields": [
        { "type": "mrkdwn", "text": "*Cluster:*\n{{ labels.cluster }}" },
        { "type": "mrkdwn", "text": "*Namespace:*\n{{ labels.namespace }}" }
      ]
    },
    {
      "type": "actions",
      "elements": [
        { "type": "button", "text": { "type": "plain_text", "text": "View Issue" }, "url": "{{ urls.issue }}" },
        { "type": "button", "text": { "type": "plain_text", "text": "View Monitor" }, "url": "{{ urls.monitor }}" },
        { "type": "button", "text": { "type": "plain_text", "text": "Silence" }, "url": "{{ urls.silence }}" }
      ]
    }
  ]
}
```

{% hint style="info" %}
This payload structure is fixed and cannot be customized. Values shown with `{{ }}` are dynamically populated from your monitor configuration. If you need a custom message format, use a [Generic Webhook](/automate/connected-apps/generic-webhook.md) instead.

**Test mode:** When using "Test the connection", the `status` field will be "test" and other fields may contain placeholder values.
{% endhint %}

#### Payload Field Reference

| Field          | Description                                                                                                                                           |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| `summary`      | Issue title from the alert                                                                                                                            |
| `status`       | Alert state: "alerting", "resolved", or "test" (during connection testing)                                                                            |
| `severity`     | Monitor severity (S1, S2, S3, S4)                                                                                                                     |
| `monitor_name` | Name of the monitor                                                                                                                                   |
| `value`        | The value that triggered the alert                                                                                                                    |
| `description`  | Monitor description with variable expansion                                                                                                           |
| `labels.<key>` | Individual label values using `labels.cluster`, `labels.namespace`, etc. Only labels defined in the monitor's group-by or custom labels are available |
| `urls.issue`   | Link to investigate the issue                                                                                                                         |
| `urls.monitor` | Link to the monitor configuration                                                                                                                     |
| `urls.silence` | Link to silence the alert                                                                                                                             |


---

# 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/slack-webhook.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.