> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/settings/integration-disconnect-alert.md).

# Integration Disconnect Alert

When an integration disconnects (an expired token, a revoked permission, a password change on the connected account), HockeyStack stops syncing data from that source. Disconnect alerts email the right people as soon as that happens, so they can reconnect before your reports fall behind.

### How it works

* When an integration disconnects, HockeyStack sends an alert email to your recipients.
* If it is still disconnected, reminders go out **7, 14, and 21 days** after the disconnect.
* Reminders stop as soon as the integration is reconnected.

### Where to find it

Go to **Workspace Settings → Integration Alerts**.

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2Fub6Jq8zHhXm0f9NQaxYt%2FScreenshot%202026-11-03%20at%203.35.42%E2%80%AFPM.png?alt=media&amp;token=2298d299-b572-488b-9133-56b6257aeb04" alt=""><figcaption></figcaption></figure>

### Set default recipients

**Default recipients** get alerts for every integration, unless you've set something different for a specific integration.

* **Leave the field empty** to email the workspace owner and all workspace admins.
* **Add email addresses** by typing them and pressing **Enter**, separating them with commas, or pasting a list.
* You can add **up to 50 recipients**.

### Set recipients per integration

Under **Per-integration recipients**, you'll see every connected integration and its current status:

* :white\_check\_mark:**Connected**: syncing normally.
* :no\_entry:**Disconnected since \[date]**: not syncing; alerts and reminders are running.
*

Click an integration to expand it. From there you can:

* **Use workspace default** to send to the default recipients
* **Custom recipients** to send its alerts to different peopl&#x65;**.** For example, send Google Ads and LinkedIn Ads alerts to your paid media team and Salesforce alerts to RevOps
* **No emails** to turn alerts off

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2F0FKhttodAsHauEzvfusW%2FScreenshot%202026-11-03%20at%203.39.02%E2%80%AFPM.png?alt=media&amp;token=2e435bc1-6fe5-47fe-89a7-502df8523a51" alt=""><figcaption></figcaption></figure>

### Reconnecting an integration

When you get an alert, reconnect the integration from **Atlas → Integrations**. You'll need to sign in with an account that has access to the connected tool. When the status changes back to **Connected**, reminder emails stop.


---

# 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.hockeystack.com/marketing-intelligence/settings/integration-disconnect-alert.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.
