> 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/integrations/connected-apps.md).

# Connected Apps

{% 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 %}

{% hint style="info" %}
Admin permissions are required for creating and editing Connected Apps.\
Reader permissions can be used for listing the existing Apps.
{% endhint %}

<figure><img src="/files/9VdkV3tFPNJuk5ydNbTG" alt=""><figcaption></figcaption></figure>

### Supported App Types

| App Type                                                               | Description                                                                                              |
| ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| [**Slack App**](/use-groundcover/connectors/slack.md)                  | Send notifications to selected Slack channels via the groundcover Slack App (supports per-rule channels) |
| [**Slack Webhook**](/integrations/connected-apps/slack-webhook.md)     | Send notifications to a single Slack channel via an incoming webhook URL                                 |
| [**PagerDuty**](/integrations/connected-apps/pagerduty.md)             | Send notifications to a PagerDuty service directory using a Routing Key                                  |
| [**Incident.io**](/integrations/connected-apps/incident.io.md)         | Send notifications to incident.io using an Alert Event URL                                               |
| [**Rootly**](/integrations/connected-apps/incident.io-1.md)            | Send notifications to Rootly using a Generic Webhook with an API Key                                     |
| [**Generic Webhook**](/integrations/connected-apps/generic-webhook.md) | Send notifications to any webhook, including authentication, headers, and payload                        |
| [**OpsGenie**](/integrations/connected-apps/opsgenie-integration.md)   | Send notifications to an OpsGenie team using an Integration API Key                                      |

### Add a Connected App

1. Go to **Settings → Connected-Apps**
2. Click the app type you want to add
3. Fill in the required fields:
   * **Integration Name**: A friendly name for this connection (e.g., `prod-alerts-channel`)
   * **Integration Details**: The URL, Secret, Key, etc..
4. Click **Save**

{% hint style="info" %}
The **Slack App** is a special case — selecting it from the Connected Apps page opens the same Slack App setup flow that lives under **Integrations → Connectors → Org Connectors**. The connector requires extra one-time setup in Slack (creating an app from a manifest, generating an App-Level Token, and OAuth authorization). See [Slack](/use-groundcover/connectors/slack.md) for the full setup walkthrough. Once configured, the Slack App appears in this list alongside the other Connected Apps and can be used in [Notification Routes](/use-groundcover/monitors/notification-routes.md) and monitors.
{% endhint %}

### Managing Connected Apps

The Apps page shows all your configured integrations in a table with:

* **Name**: The integration name you assigned
* **Type**: The app type (e.g., Slack Webhook)
* **Creator**: Who set it up
* **Used By**: Which notification routes reference this app
* **Created at**: When it was added

#### Edit or Delete

Hover over any row to reveal the Edit and Delete buttons.

{% hint style="warning" %}
Connected App being used by Notification Routes or Monitors cannot be deleted. Check the "Used By" column is empty before attempting to delete.
{% endhint %}

### Next Steps

After setting up your connected apps, create Notification Routes and Monitors to start routing issues to them.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.groundcover.com/integrations/connected-apps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.