Skip to main content
Chert for Slack connects a Chert project to a workspace channel. Reply notifications land in Slack for fast triage, and @Chert Agent can answer campaign questions or run channel-level operations.

When to use it

Use Slack when operators live in a channel and need to review replies, approve actions, or monitor campaign health without opening the CRM for every message.
Best fitShared reply triage, campaign monitoring, and lightweight operator actions.
Automation fitSlack cards should notify the team when a lead replies.
Not forFull CRM data entry. Slack complements Salesforce, HubSpot, or the Chert console.

What gets connected

ItemWhere it appearsWhat it does
Chert NotificationsSlack app installPosts lead reply cards and supports thread-based triage.
Chert AgentSeparate Slack app installResponds to @Chert Agent mentions for campaign operations.
Channel bindingChert SettingsRoutes one Chert project to one Slack channel; switchable without reinstalling.
Bot tokensChert server-side storageStored per project and never exposed to the browser.
CanvasesBound Slack channelOptional Overview, Daily Summary, and Lead Lists canvases.
Signing-secret verificationChert inbound event handlerVerifies every inbound Slack event.
The two apps are independent installs. You can install either or both into the same channel.

OAuth scopes

Both apps request the same scopes because reply cards, app mentions, and canvases share the same workspace surface.
ScopeWhy Chert needs it
chat:writePost reply cards, agent responses, and alerts.
chat:write.publicPost in public channels before explicit bot invite.
channels:readPopulate the Settings channel picker.
groups:readInclude private channels in the picker.
canvases:writeCreate and update Overview, Daily Summary, and Lead Lists canvases.
Canvas writes will silently no-op for installs that predate the canvases:write scope. Reinstall to grant it.

Minimal usage example

After installing Chert Notifications and binding a channel:
  1. A lead replies to an outbound iMessage.
  2. Chert posts a reply card in the bound Slack channel.
  3. An operator reviews the conversation tail and either opens the CRM deep link or replies in the Slack thread for triage.
For campaign operations, mention the agent in the same channel:
@Chert Agent how are we doing today?
Slack notification flow

Next steps

Install

OAuth install for both apps and channel binding.

Configuration

Per-project flags, notification routing, and the Nth-reply filter.

Notifications

Card anatomy and thread-reply triage.

Security

Token storage, signing-secret verification, and data handling.