Release Notes

Product News: Advanced Notifications for Slack, Discord, Telegram, Email, and Webhooks

A new notification engine sends Concord events to Slack, Discord, Telegram, email, or your own systems: privacy requests, scan issues, trust center access, failing control tests, vendor reviews, and risk reviews.

Concord Team · Published Fri Nov 06 2026

Product News: Advanced Notifications for Slack, Discord, Telegram, Email, and Webhooks

Privacy and compliance work tends to show up where your team already is, not where it's tracked. A privacy request arrives, a scan finds a problem, a buyer asks for trust center access, and someone needs to know now. Concord's notifications now run on a new engine: Send Notification delivers the events you choose to the places your team works, whether that's a Slack channel, a Discord channel, a Telegram chat, an email inbox, or your own systems.

A New Notification Engine

Set one up from Actions > Browse Catalog. Pick the events it listens for, how often it may send, and where it goes. One notification can listen for several events and send to several destinations, and you can set up as many as you like.

  • Choose how often. Every time, or at most once every 15 minutes, hour, day, or week, for each event and project.
  • Write your own message. Leave it empty for Concord's default message, or write your own and use Insert Field to add details from the event, such as the project name or a link back to Concord.
  • Test it first. Send Test sends a sample to any destination right away.
  • See what was sent. Activity shows every run with each destination's outcome: delivered, or the reason it wasn't.

Notifications never carry a requester's personal details, such as their name or email address, so personal data doesn't spread into Slack channels, chat histories, or inboxes, and stays in one place when someone asks you to delete it. Each message says what kind of request it is and links straight to it in Concord.

Slack, Discord, and Telegram

Connect a chat app once under Integrations, then pick it in any notification.

  • Slack: allow the Concord app in your workspace, then pick a channel. Private channels show up once someone invites the Concord app.
  • Discord: pick a server and channel, and Concord posts through a webhook it adds to that channel.
  • Telegram: send a direct message to the Concord bot, or add it to a group chat, and link the chat with the code the bot replies with.

Signed Webhooks

Send events to your own systems as an HTTPS POST with a JSON body, signed so you can check it came from Concord. Every retry carries the same body and delivery ID, so your system can drop duplicates. When your endpoint has a problem that may pass, such as a timeout or a server error, Concord tries again over the next two hours.

What You Can Be Notified About

  • Privacy requests: each new request, plus a daily or weekly summary of received, resolved, due soon, and overdue requests.
  • Scans: a scan found issues.
  • Tasks: a task was assigned.
  • Trust center: an access request needs review, access was granted automatically, or an NDA was signed.
  • Controls: a control test is failing.
  • Vendors: a vendor review is due, or a vendor document is about to expire.
  • Risks: a risk review is overdue.

Get Started

Send Notification and email work on every plan, and chat apps and webhooks are on paid plans. See Sending Notifications for the setup steps, or book a demo and we'll walk you through it.