> For the complete documentation index, see [llms.txt](https://learn.heeler.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.heeler.com/tenant-admin-guide/integrations.md).

# Integrations

The **Integrations** tab is where you connect Heeler to the tools your teams already use to communicate (e.g., Slack, Teams), track work (e.g., Jira, Linear) and engineering platforms (e.g., Port.io). Integrations are what let workflows and guardrails actually reach people: route a ticket, send a message, file an issue, etc.

### Where to find it

Open the **gear icon** in the top-right → **Integrations** tab. This is a flat list (no sub-sections).

URL: `https://app.heeler.com/administration/integrations`

### Quick start

[See the Integration Setup documentation](/getting-started/integration-setup.md). 

### Reference

#### Table columns

| Column         | Description                                                           |
| -------------- | --------------------------------------------------------------------- |
| **Name**       | The integration name (often customizable, e.g., "Engineering Slack"). |
| **Health**     | Whether the connection is active.                                     |
| **Date Added** | When the integration was first set up.                                |

#### Actions

* **Add Integration** — start a new integration setup flow.
* Clicking a row opens detail where you can refresh credentials, rename, or disconnect.

### How integrations are used

After you connect an integration, it becomes available in two places:

1. **Workflows** — choose which integration to send notifications and tickets through (e.g., "post to #appsec on Slack", "file a Jira issue in the SECURITY project").
2. **Connection Mapping → Teams** — each Team can have default channels (Slack, Jira project, etc.) so workflows can route on a per-team basis without re-specifying defaults.


---

# 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://learn.heeler.com/tenant-admin-guide/integrations.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.