Skip to main content
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

1

Install Marketer

Go to Integrations → Slack and select Add to Slack. If access changed, use Reconnect Slack instead.
2

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.
3

Choose the alerts channel

In Finish Slack setup, select Alerts channel. Reports, spend alerts, and approvals post here.
4

Set delivery preferences

Configure Post to Slack, Email alerts, Notify for, and the event groups. Select Save preferences or Save routing as shown.
5

Link your account

Finish the personal link so Marketer can deliver direct messages and attribute Slack requests to your Marketer identity.
The detail page identifies Workspace, Bot user, and Connected. Verify all three before testing messages.

​
Read the connection state

​
Configure notification routing

Slack uses the same workspace notification policy as Settings → Notifications. 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:

​
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.
Last modified on August 9, 2026