Slack, Teams & Discord
Route findings and events into your team's Slack workspace, Microsoft Teams tenant, or Discord server - set up credentials, pick a default channel and message the Safeguard bot.
Slack, Teams & Discord
Safeguard can push findings and platform events into a team's existing chat tool, a Slack workspace, a Microsoft Teams tenant, or a Discord server, so security signal shows up where people already work. Each is a dedicated integration with its own connection setup, a credential validation step and a default channel. They are under Settings → Integrations.
If you are looking for the list of systems Safeguard can pull compliance evidence from, see Connectors. This page covers the notification and chat feature.
Which platform should I use?
| Platform | Auth options | Where notifications go |
|---|---|---|
| Slack | Bot Token or Incoming Webhook | The default channel you pick during setup |
| Microsoft Teams | Bot Framework or Incoming Webhook | The default team and channel you pick during setup |
| Discord | Bot Token or Webhook | The default channel you pick during setup |
All three are set up the same general way: pick an authentication type, enter its credentials, let Safeguard validate them and pull your channel (or team or server) list, then pick where notifications go. Bot-based options give you a picker; webhook options post to the one channel the webhook is bound to.
Setting up Slack
Going the BOT_TOKEN route? Install the Safeguard Slack app to your workspace first - Slack hands you a Bot User OAuth Token (xoxb-...) at the end of the install, which you then paste into the drawer below. Installing the app does not create the integration by itself: Safeguard has no Slack OAuth callback, so the token hand-off is manual either way.
-
In Safeguard, go to Settings → Integrations and click Connect on the Slack tile.
-
On the Credentials step, fill in:
Field Required Notes Integration Name Yes Must be unique across your integrations Description No Authentication Type Yes BOT_TOKENorINCOMING_WEBHOOKBot Token Only for BOT_TOKENA Slack app's bot token ( xoxb-...), from OAuth & Permissions in your Slack appWebhook URL Only for INCOMING_WEBHOOKA Slack Incoming Webhook URL ( https://hooks.slack.com/services/...) -
Click Next. Safeguard validates the credentials first - for
BOT_TOKEN, a successful validation also fetches your workspace's channel list;INCOMING_WEBHOOKcredentials validate but skip channel listing, since a webhook is already bound to one channel. -
On the Channel step:
- Bot Token: pick a Default Channel from the list Safeguard just fetched. If no channels appear, the bot hasn't been invited to any channel yet - see Troubleshooting.
- Incoming Webhook: there's nothing to pick - messages go to whatever channel the webhook URL is bound to. You can optionally type in a display name for that channel.
Auth type comparison: BOT_TOKEN ("Bot Token (Full Access)" in the UI) gives Safeguard a channel picker across your workspace, so you can choose which channel gets notifications. INCOMING_WEBHOOK ("Incoming Webhook (Send Only)") is faster to set up but only ever posts to the one channel the webhook was created for.
Setting up Microsoft Teams
-
Go to Settings → Integrations and click Connect on the Teams tile.
-
On the Credentials step, fill in:
Field Required Notes Integration Name Yes Must be unique across your integrations Description No Authentication Type Yes BOT_FRAMEWORKorWEBHOOKWebhook URL Only for WEBHOOKA Teams Workflows (Power Automate) webhook URL, or an Office 365 connector webhook URL. See the accepted URL shapes below Microsoft Tenant ID Only for BOT_FRAMEWORKYour Azure/Entra tenant GUID App ID (Client ID) Only for BOT_FRAMEWORKThe registered app's client ID App Secret (Client Secret) Only for BOT_FRAMEWORKThe registered app's client secret All three Bot Framework fields are required together - Safeguard won't let you proceed with only some of them filled in.
-
Click Next. Credentials are validated first; for
BOT_FRAMEWORK, a successful validation also fetches the Microsoft Teams teams your app can see.WEBHOOKcredentials validate but there's no team/channel list to fetch, since the webhook already targets one channel. -
On the Channel step:
- Bot Framework: pick a Team, then pick a Channel within that team - Teams' hierarchy is team-then-channel, not a flat channel list like Slack or Discord.
- Webhook: nothing to pick; you can optionally type in a display name for the target channel.
Auth type comparison: WEBHOOK ("Incoming Webhook (Send Only)") posts to a single, pre-bound channel. It accepts both Teams Workflows (Power Automate) webhooks and Office 365 connector webhooks. BOT_FRAMEWORK ("Bot Framework (Full Access)") requires registering an Azure AD app and grants Safeguard visibility into your teams and channels, so you can pick which team and channel gets the default notifications.
Teams webhook URLs
Paste the URL exactly as Teams gives it to you. Safeguard accepts these shapes and rejects anything else:
| Kind | URL shape |
|---|---|
| Teams Workflows (Power Automate) | https://prod-NN.<region>.logic.azure.com/workflows/<id>/triggers/<name>/paths/invoke?...&sig=<signature> or https://<environment>.environment.api.powerplatform.com/powerautomate/automations/direct/workflows/<id>/triggers/<name>/paths/invoke?...&sig=<signature> |
| Office 365 connector | https://outlook.office.com/webhook/..., https://outlook.office365.com/webhook/... or https://<tenant>.webhook.office.com/webhookb2/... |
The rules:
- The host must be a Microsoft host from the table above, on the default HTTPS port. The check matches the whole host name, so a URL that only contains a Microsoft name somewhere in its path or in a longer host does not pass.
- The scheme must be
https. URLs with a username or password in them, IP addresses and fragments are refused. - A Workflows URL must carry its
sigsignature in the query string. Teams includes it when you copy the URL from the Workflows trigger, so paste the whole thing; a URL without the signature cannot be called and is refused at validation.
To create a Workflows webhook, use the Teams Workflows template "Post to a channel when a webhook request is received", then copy the URL it shows. Safeguard posts to Workflows webhooks as an Adaptive Card. Office 365 connector webhooks that are already configured keep working and keep receiving the card format they always did. Safeguard does not follow redirects when it posts to your webhook.
Setting up Discord
-
Go to Settings → Integrations and click Connect on the Discord tile.
-
On the Credentials step, fill in:
Field Required Notes Integration Name Yes Must be unique across your integrations Description No Authentication Type Yes BOT_TOKENorWEBHOOKBot Token Only for BOT_TOKENFrom the Bot section of a Discord application in the Discord Developer Portal Webhook URL Only for WEBHOOKA Discord channel webhook URL ( https://discord.com/api/webhooks/...) -
Click Next. Credentials are validated first - for
BOT_TOKEN, a successful validation also fetches the list of Discord servers (guilds) the bot has been added to. ForWEBHOOK, the validation response returns the webhook's own channel directly, since a Discord webhook is scoped to a single channel. -
On the Server & Channel step:
- Bot Token: pick a Server, then pick a Channel in that server - Safeguard filters the channel list down to text channels only.
- Webhook: nothing to pick; you can optionally type in a display name for the channel.
Auth type comparison: BOT_TOKEN ("Bot Token (Full Access)") gives Safeguard a server/channel picker across every Discord server the bot has joined. WEBHOOK ("Webhook URL (Send Only)") is quicker but limited to the one channel the webhook is bound to.
Credential validation, every time
For all three platforms, Safeguard validates credentials in a dedicated step before it ever tries to list channels, teams, or servers - you can't get to a channel picker with credentials Safeguard hasn't already confirmed work. If validation fails (revoked token, wrong scopes, malformed webhook URL, wrong tenant), you get an inline error and the flow doesn't advance. This is the same underlying step whether you're creating a new integration or editing an existing one with new credentials.
Messaging the Safeguard bot
In Slack, Discord and Microsoft Teams you can message the Safeguard bot and ask about your security and compliance work, for example "which controls are failing?" or "list critical vulnerabilities". The bot answers as your own Safeguard account, with your own access, so you may be asked to link your account first. help shows what it can do.
FAQ & Troubleshooting
Credential validation fails immediately.
Double-check you're using the right credential for the auth type you selected - a Slack bot token (xoxb-...) won't validate under INCOMING_WEBHOOK, and vice versa. For Teams BOT_FRAMEWORK, all three of Tenant ID, App ID, and App Secret must be correct together; a single wrong value fails validation with no partial credit.
No channels show up in the Slack or Discord channel picker.
This is the single most common setup snag with bot-based (not webhook-based) chat integrations: the bot has valid credentials, but it hasn't actually been added to any channel or server yet. In Slack, invite the bot to at least one channel (/invite @your-bot-name in that channel) and retry - Safeguard's own UI message here is literally "No channels found. Make sure the bot is invited to at least one channel." In Discord, make sure the bot has actually been added to a server (guild) via its OAuth invite link, with permission to view the channels you expect to route to - note that Discord's picker doesn't show an equivalent "no servers found" message; if your bot has no servers, the Select Server step just sits on "Loading servers..." indefinitely rather than telling you to invite the bot, so don't assume it's still working if it hasn't resolved after a few seconds.
A Teams webhook URL is rejected.
Check it against the shapes in Teams webhook URLs: a Microsoft host, https, and for a Workflows URL the sig parameter. A URL that was cut off when copying, or one that lost its query string, fails for that reason.
Teams shows no teams, or no channels within a team. Confirm the Azure AD app tied to your App ID/App Secret has actually been granted access to the tenant and to the specific teams you expect to see - an app that validates successfully can still have zero visibility into teams it hasn't been added to.
Should I use a webhook or a bot/app integration? Webhooks (Slack Incoming Webhook, Discord Webhook) are the fastest to set up and are fine if you only want notifications in one fixed channel. Bot-based integrations (Slack Bot Token, Teams Bot Framework, Discord Bot Token) take more setup but give you a channel or team picker, and they are what you need to message the bot. For Teams, a Workflows webhook is enough for one fixed channel; use Bot Framework when you want the team and channel picker or want to message the bot.
How is this different from the Slack/Teams/Discord entries on the Connectors page? The Connectors page lists these as generic OAuth evidence sources for compliance. The integrations on this page are dedicated notification features with their own setup drawer, credential validation and default-channel picker.
I'm editing an existing integration and it's not asking me to re-enter credentials. That's expected, not a bug: if you leave the Bot Token / Webhook URL / App Secret fields blank while editing and don't change the authentication type, Safeguard reuses the credentials already on file and skips re-validation for that step. Only fill in a credential field if you're actually rotating it.
Related
- Connectors - the broader connector catalog.
- Integrations - the full integrations index.
- Webhooks & Events - Guard alert webhooks to your own endpoint.
- Guardrails & Enforcement - policy gates in your pipeline.
Webhooks & Events
How Safeguard tells your systems that something happened - scan results over the CI scan API and notifications in your team's chat tool.
Safeguard AI SDKs
Official TypeScript, Python and Go SDKs for Safeguard AI. Send a prompt from your own code, stream the answer, and keep conversations, with a secret key that carries the ai:chat scope.