Slack, Discord and webhooks

Beyond the personal email digest, a workspace can push a summary to Slack, Discord, or any JSON endpoint on a schedule. You set these up under Settings → Integrations, in the Webhooks & digests section. This is an admin and owner task.

Add a destination

Choose Add destination and fill in:

• Name: a label for the destination, such as Team Slack · #dev-signals.
• Frequency: Daily (morning) or Weekly (Monday morning).
• Webhook URL: paste the incoming-webhook URL. Slack and Discord URLs are detected automatically; anything else is sent as a generic JSON payload.
• Include sections: toggle which blocks appear (Net sentiment, AI share of voice, Top signals, By source, Unanswered).
• Max signals listed: how many mentions to include, up to 50.
• Minimum priority: send everything, or only mentions at or above a priority.
• Scope: optionally limit the digest to certain sources and watchers. Leave both empty to cover everything.

Slack and Discord

Create an incoming webhook in Slack or Discord for the channel you want, then paste that URL. BackTalk formats the digest natively for each, so it reads as a proper message rather than raw JSON.

Generic JSON

Any other URL receives the digest as a JSON POST, so you can forward it into your own tooling, a serverless function, or another chat platform.

Test it, then leave it running

Use Send test to fire the current digest at a destination immediately and confirm it arrives. Each destination has an On / Off switch, so you can pause one without deleting it, and if a scheduled send ever fails the row flags it.

Destinations deliver on their chosen daily or weekly cadence. For per-person email delivery with daily, weekly or monthly options and one-click unsubscribe, see Email notifications instead.