Slack
AvailableOAuth
Slack is a notification destination, not a data source. Connect it so agent workflow results, sync failures, and campaign thresholds land in a channel your team already reads instead of waiting to be discovered in Activity Logs.
What moves, and which way
Integrations run in both directions. What follows is what this connection is for.
En Garde to Slack
- Notifications for agent workflow runs, integration errors, and campaign events you choose to alert on.
Slack to En Garde
- Delivery confirmation for the messages sent, and the channel list you pick a destination from.
Connecting it
You approve the connection on the platform itself. En Garde never sees your password — the platform hands back a token scoped to the permissions shown before you approve.
- Open Integrations in your Brand Space. The page is titled Connected Apps.
- Find the platform on the Integrations tab, using the search box or the category filter.
- Click Connect. A dialog lists the permissions En Garde will request.
- Continue to the platform. A popup opens on their site where you sign in and approve. If nothing appears, your browser blocked the popup — allow popups for En Garde and try again.
- Leave the popup open until it closes on its own. En Garde then checks the connection status and the card moves to Connected.
Worth knowing
- You approve the install against a workspace, then choose the channel messages go to. Installing to a workspace does not by itself post anything.
- Adding En Garde to a private channel requires inviting the app to that channel from inside Slack — workspace approval alone is not enough.