> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/messaging.md).

# Connect Messaging

Connect Slack, Microsoft Teams, or Google Chat so Heeler can deliver workflow notifications to the right channels.

Connect a messaging tool and Heeler can deliver **workflow notifications** — new vulnerability alerts, remediation updates, finding notifications — to the channels your teams already watch. Messaging destinations are available in workflows and in per-team, per-repository, per-service, and per-module routing.

## Supported messaging tools

<table data-view="cards"><thead><tr><th></th><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Slack</strong></td><td>OAuth — install the Heeler Slack app.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/get-started/messaging/slack.md">Slack</a></td></tr><tr><td><strong>Microsoft Teams</strong></td><td>Teams Workflows webhooks — no Azure AD app.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/get-started/messaging/microsoft-teams.md">Microsoft Teams</a></td></tr><tr><td><strong>Google Chat</strong></td><td>Incoming webhooks — Google Workspace.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/get-started/messaging/google-chat.md">Google Chat</a></td></tr></tbody></table>

<table><thead><tr><th width="200">Tool</th><th>How it authorizes</th></tr></thead><tbody><tr><td><strong>Slack</strong></td><td>OAuth app install (short-lived, auto-refreshed credentials).</td></tr><tr><td><strong>Microsoft Teams</strong></td><td>One or more per-channel <strong>webhook URLs</strong> added via <strong>Manage Webhooks</strong>.</td></tr><tr><td><strong>Google Chat</strong></td><td>One or more per-Space <strong>webhook URLs</strong> added via <strong>Manage Webhooks</strong>.</td></tr></tbody></table>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/messaging.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.