Overview - Chert

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 fit	Shared reply triage, campaign monitoring, and lightweight operator actions.
Automation fit	Slack cards should notify the team when a lead replies.
Not for	Full CRM data entry. Slack complements Salesforce, HubSpot, or the Chert console.

What gets connected

Item	Where it appears	What it does
Chert Notifications	Slack app install	Posts lead reply cards and supports thread-based triage.
Chert Agent	Separate Slack app install	Responds to `@Chert Agent` mentions for campaign operations.
Channel binding	Chert Settings	Routes one Chert project to one Slack channel; switchable without reinstalling.
Bot tokens	Chert server-side storage	Stored per project and never exposed to the browser.
Canvases	Bound Slack channel	Optional Overview, Daily Summary, and Lead Lists canvases.
Signing-secret verification	Chert inbound event handler	Verifies 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.

Scope	Why Chert needs it
`chat:write`	Post reply cards, agent responses, and alerts.
`chat:write.public`	Post in public channels before explicit bot invite.
`channels:read`	Populate the Settings channel picker.
`groups:read`	Include private channels in the picker.
`canvases:write`	Create 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:

A lead replies to an outbound iMessage.
Chert posts a reply card in the bound Slack channel.
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?

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.

​When to use it

​What gets connected

​OAuth scopes

​Minimal usage example

​Next steps