> ## Documentation Index
> Fetch the complete documentation index at: https://docs.marketer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack

> Install Marketer, finish workspace routing, link direct messages, and recover missing permissions.

Slack lets a Marketer workspace receive alerts, handle approvals, and work with the agent from Slack. Installation, notification routing, and personal direct-message linking are separate parts of setup.

## Before you connect

* Use a Marketer Owner, Admin, or Member role.
* Be able to approve or request installation of the Marketer Slack app.
* Know which Slack workspace corresponds to the active Marketer workspace.
* Choose one shared channel for reports, spend alerts, and approvals.
* Decide whether email delivery should run independently of Slack.

## Install and finish setup

<Steps>
  <Step title="Install Marketer">
    Go to **Integrations** → **Slack** and select **Add to Slack**. If access changed, use **Reconnect Slack** instead.
  </Step>

  <Step title="Approve Slack access">
    Review the current Slack permissions. A reconnect can be required to add support for group DMs, private channels, file uploads, or reactions.
  </Step>

  <Step title="Choose the alerts channel">
    In **Finish Slack setup**, select **Alerts channel**. Reports, spend alerts, and approvals post here.
  </Step>

  <Step title="Set delivery preferences">
    Configure **Post to Slack**, **Email alerts**, **Notify for**, and the event groups. Select **Save preferences** or **Save routing** as shown.
  </Step>

  <Step title="Link your account">
    Finish the personal link so Marketer can deliver direct messages and attribute Slack requests to your Marketer identity.
  </Step>
</Steps>

The detail page identifies **Workspace**, **Bot user**, and **Connected**. Verify all three before testing messages.

## Read the connection state

| State                  | Meaning                                                                | Next action                                    |
| ---------------------- | ---------------------------------------------------------------------- | ---------------------------------------------- |
| **Status unavailable** | The latest Slack check failed and the last-known installation remains  | Refresh before changing it                     |
| **Disconnected**       | The app is not installed for this Marketer workspace                   | Select **Add to Slack**                        |
| **Reconnect needed**   | Slack rejected the token or the installation lacks current permissions | Select **Reconnect Slack**                     |
| **Finish setup**       | Installation exists, but required routing is incomplete                | Choose the alerts channel and save preferences |
| **Connected**          | Installation and required workspace setup are present                  | Send a test and verify the personal link       |

## Configure notification routing

Slack uses the same workspace notification policy as **Settings** → **Notifications**.

| Control                   | Effect                                                                |
| ------------------------- | --------------------------------------------------------------------- |
| **Post to Slack**         | Master switch for Slack delivery                                      |
| **Channel**               | Shared destination; the bot can join the chosen channel automatically |
| **Email alerts**          | Independent master switch for email; requires at least one recipient  |
| **Everything**            | Sends information, warnings, and critical events externally           |
| **Warnings and critical** | Keeps lower-severity events in the app                                |
| **Critical only**         | Externally delivers only critical events                              |

Event groups use these exact meanings:

* **Performance** — Spend spikes, ROAS drops, anomalies.
* **Account health** — Token expiry, sync failures, disconnects.
* **Approvals** — When the agent needs a decision from you.
* **Agent activity** — Run completions, creative ready.
* **Budget** — Budget changes and spend-cap warnings.
* **Billing & team** — Billing issues, member changes.

The in-app feed keeps notifications regardless of external delivery. Approval DMs can go to the person they belong to rather than the shared alerts channel.

## Work with the agent in Slack

* In a direct message, Marketer answers each message.
* In a channel, mention **@Marketer** when you need a response. It can continue useful account or task context in a thread.
* Longer work can post progress and approval requests.
* Reactions communicate state: 👀 working, ✅ answered, and ⚠️ failed.

Available slash commands:

| Command                   | Purpose                                 |
| ------------------------- | --------------------------------------- |
| `/marketer status`        | Check current Marketer status           |
| `/marketer stop <run-id>` | Stop the specified run                  |
| `/marketer whoami`        | Check which Marketer identity is linked |
| `/marketer <prompt>`      | Send a request to Marketer              |

## Add channels safely

The bot can join additional channels for conversation. Keep the configured alerts channel as the protected routing destination for shared notifications, and mention the bot in other channels when you need it.

If channel listing fails after an older installation, use **Reconnect Slack** to grant the current permissions. Do not disconnect first unless you intend to replace the entire installation.

## Recover account linking

If the Slack email and Marketer email do not match, use **Open Slack to finish** and direct-message the bot to complete the link. Then run `/marketer whoami` and confirm the expected identity.

An installation maps to the active Marketer workspace. To connect the same Slack organization to another Marketer workspace, switch workspaces first and install or configure Slack there separately.

## Disconnect impact

Disconnecting removes the Slack app for this workspace, stops routed alerts, and clears workspace routing and personal links. Review active approvals, alert ownership, and replacement delivery before confirming.

## Next step

Send a harmless test, run `/marketer whoami`, and verify one notification in the configured channel before relying on Slack for approvals or critical alerts.


## Related topics

- [Notifications and billing](/workspace-admin/notifications-and-billing.md)
- [Troubleshoot integrations](/integrations/troubleshooting.md)
- [Reports, alerts, guarded actions, and runs](/product-guides/workflows-reports-alerts-and-runs.md)
- [Branding and Autofills](/workspace-admin/brand-and-autofills.md)
- [Workflows](/product-guides/workflows.md)