> 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/operate/heeler-in-slack.md).

# Heeler in Slack

Query findings, investigate vulnerabilities, and check SLO status from Slack — with slash commands, the @Heeler assistant, and automatic link previews.

In Slack, Heeler answers questions about **findings, vulnerabilities and SLO status**. There are two ways to interact — precise **slash commands** and the conversational **`@Heeler`** assistant — and Heeler also previews any finding link you paste into a channel.

{% hint style="info" %}
**Before you start:** the **Heeler Slack app must be installed** in your workspace (an admin connects it under [Configure Integrations → Slack](/mrecEO40m5D6bt7Pq5pE/get-started/messaging/slack.md)), and each person links their own Heeler account with `/heeler connect` (below). What the assistant can do for you depends on **your** Heeler access level.
{% endhint %}

| Mode               | How to trigger       | Best for                                       |
| ------------------ | -------------------- | ---------------------------------------------- |
| **Slash commands** | `/heeler <command>`  | Precise, repeatable queries with exact filters |
| **@mention**       | `@Heeler <question>` | Freeform exploration and follow-up questions   |

## Link your account

Before your first query, link your Slack identity to your Heeler account:

1. Run `/heeler connect`. Heeler replies with a **Connect** link.
2. The link ties your Slack identity to the Heeler account **you're already signed into in your browser** — so make sure you're logged into Heeler first.
3. Follow the link; Heeler DMs you **Confirm** / **Cancel** buttons to finish. The request expires after **10 minutes** — re-run `/heeler connect` if it lapses.

Once linked, you can run any command below. Use `/heeler status` to see which Heeler user and tenant you're linked to, and `/heeler disconnect` to unlink (effective immediately).

## Slash commands

Slash commands give you direct, deterministic access to your Heeler data — each maps to a specific query and returns exactly what you asked for. Results come back as an **ephemeral message visible only to you**. Running `/heeler` with no arguments (or an unrecognized command) shows the help text.

| Command                                                             | What it does                                                                                                                                          |
| ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| `/heeler findings [severity] [--repo <repo>] [--service <service>]` | Summarize active dependency-vulnerability findings, optionally scoped by severity, repository, or service.                                            |
| `/heeler slo`                                                       | Show dependency-vulnerability SLO pressure — grouped into **Overdue** and **Due in the next 7 days**.                                                 |
| `/heeler vuln <CVE\|GHSA>`                                          | Look up a specific vulnerability — severity, title, and how many active findings you have for it.                                                     |
| `/heeler summary --service <name> \| --repo <name>`                 | Posture summary for one service **or** repository. Exactly one of `--service` / `--repo` is required.                                                 |
| `/heeler secrets [--repo <name>]`                                   | Count active exposed secrets, optionally scoped to a repository.                                                                                      |
| `/heeler remediation --repo <name>`                                 | The prioritized remediations for a repo, grouped by package so you see which single upgrade closes the most findings. `--repo` required.              |
| `/heeler pkg <package> [--ecosystem <ecosystem>]`                   | Investigate a package across repositories — open findings, affected repos/services, top CVEs. Accepts a name, a name + `--ecosystem`, or a full PURL. |
| `/heeler connect` · `/heeler status` · `/heeler disconnect`         | Link, check, or unlink your account.                                                                                                                  |
| `/heeler help`                                                      | Show the available commands.                                                                                                                          |

{% hint style="info" %}
**Ambiguous names.** If a repository or service name matches more than one entity, Heeler lists the candidates and asks you to re-run scoped to the one you meant.
{% endhint %}

A few examples:

```
/heeler findings critical
/heeler findings --repo payments-api high
/heeler vuln CVE-2024-1234
/heeler summary --service checkout
/heeler pkg log4j
```

## Ask @Heeler

Mention **`@Heeler`** in any channel to ask security questions in plain English. The assistant queries your real Heeler data and answers inline — grounded in what's actually in your platform.

```
@Heeler show me critical vulnerabilities in the payments service
@Heeler which of those has an active exploit?
@Heeler what packages are affected by CVE-2024-1234?
```

`@Heeler` can also answer **guardrail** questions — guardrail status, PRs blocked by guardrails, or recent violations.

* **Conversational context.** Heeler retains a thread for **2 hours**, so a follow-up ("which of those has a fix available?") does not need the context repeated.
* **Disambiguation.** When a question is ambiguous — you say "payments" and several repositories match — Heeler lists the candidates and asks you to re-run scoped to the one you meant.
* **Depth limit.** Each turn makes up to **25** data lookups; if a question is complex enough to hit that, Heeler stops and asks you to narrow it rather than returning a partial answer.

{% hint style="warning" %}
**What the assistant can change depends on your access level.** For **read-only** users it has read tools only — it can't change any Heeler data. For **admins with override permission**, it additionally has SLO-override tools (create / extend), and uses them **only when you explicitly ask** for that specific write.
{% endhint %}

**Slash command or @mention?**

| Use `@Heeler` when…                    | Use slash commands when…                       |
| -------------------------------------- | ---------------------------------------------- |
| You're not sure of the exact syntax    | You know exactly what you want                 |
| You want to explore and ask follow-ups | You need a consistent, repeatable query        |
| You want a plain-English explanation   | You're running a query the same way every time |

## Link previews

Paste a Heeler finding or service link (an `app.heeler.com` URL) into a message and Heeler automatically attaches an **inline preview card** with the security context — no command needed. Previews cover dependency (SCA) findings, code (SAST) findings, vulnerabilities, and services.

{% hint style="info" %}
Previews require Heeler to be a **member of the channel**. If no preview appears, invite it with `/invite @Heeler` and confirm your account is linked with `/heeler status`.
{% endhint %}

## Troubleshooting

* **A command did nothing.** Check your link with `/heeler status`; if it shows you're not connected, run `/heeler connect`.
* **Your connection stopped working.** Re-run `/heeler connect` to re-link.
* **`/heeler summary` asks for a service or repo.** Provide exactly one — e.g. `/heeler summary --service payments-api`.
* **Link previews aren't working.** Invite Heeler to the channel (`/invite @Heeler`) and try the `app.heeler.com` link again.
* **Can `@Heeler` change my data?** Only if you're an admin with override permission, and only when you explicitly ask for an SLO override. Read-only users get read tools only.

## Related

* [Configure Integrations → Slack](/mrecEO40m5D6bt7Pq5pE/get-started/messaging/slack.md) — install and connect the Heeler Slack app (the setup this page assumes).
* [MCP Server](/mrecEO40m5D6bt7Pq5pE/prevent/mcp.md) — Heeler's live security context, inside your AI coding agent.
* [Service Level Objectives (SLOs)](/mrecEO40m5D6bt7Pq5pE/operate/service-level-objectives-slos.md) — the SLO clock the `slo` command and overrides act on.


---

# 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/operate/heeler-in-slack.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.