> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/connectors/slack.md).

# Slack

## Overview

The Slack connector lets Nullify reach engineers where they already work. Once connected, Nullify can:

* **Escalate findings** that need developer action — an open fix PR that hasn't been reviewed, a fix that's blocked, or a secret that needs rotating.
* **Send campaign nudges and informational updates** to keep teams aligned on remediation.
* **Take replies in-thread**, so engineers can respond without leaving Slack.

Messages are delivered asynchronously, so teams stay productive inside Slack without hopping between tools.

## Ask Nullify directly

Engineers don't have to wait for a message — they can start a conversation with Nullify any time by **`@mention`-ing** it, sending it a **direct message**, or **replying in any thread** it's part of. Ask about:

* **Findings** across code, dependencies, containers, secrets, cloud posture, and pentests.
* **Remediation campaigns** and their progress.
* **Security metrics and trends.**
* **Threat investigations** and which repositories are affected.

Nullify replies in plain language and links to the relevant place in the dashboard. From a Slack thread you can also answer and resolve the [action items](/capabilities/working-with-nullify.md) Nullify raises — approve or dismiss an escalation, answer a question, or assign a team. For broader state changes like allowlisting a finding, triggering a fix, or creating a ticket, Nullify points you to the dashboard.

## Connect Slack

Connecting Slack is a one-time authorization — there's no app to build or token to paste.

1. Log in to the Nullify Dashboard.
2. Go to **Configure → Connectors → Slack**.
3. Click **Connect** and authorize the Nullify Slack app in your workspace via OAuth.

Once authorized, Nullify verifies the connection and marks the connector as **Enabled**. You're then ready to choose where escalations go — see [Configuring notifications & escalations](/connectors/slack/slack-notifications.md).