Slack
This notifier can send messages to a Slack channel for incident lifecycle events (from Internal and/or Public Monitoring), honeytoken alerts.
To set up your Slack integration, provide a Slack incoming webhook URL in the Slack settings section and configure which events you want to receive notifications for.
How to integrate
-
Visit Slack API: Create an App.
-
Create a new application for GitGuardian.

-
Enable the Incoming Webhooks feature.

-
Generate a new webhook.

-
Copy the generated webhook URL.

-
Paste the webhook URL in the Slack integration section of your GitGuardian dashboard settings.

Team-level configuration:
- Personal workspace: You can only configure alerting on the 'All-incidents team'.
- Business workspace: You can configure the integration on any team:
- Create it within the 'All-incidents team' to receive notifications for all workspace incidents.
- Create it within a specific team to receive notifications only for that team's incidents.
This can be done directly from the integration page or from the team page.
-
Select the events you would like to subscribe to and receive.
Events
You can subscribe to the following events from GitGuardian Internal Monitoring and/or GitGuardian Public Monitoring (if your workspace and team have access to Public Monitoring):
| Name | Description |
|---|---|
| New incident detected | A new incident has been detected. |
| New occurrence detected | A new occurrence has been detected for this incident. |
| Incident Validity changed | The validity has been updated for this incident. |
| Incident status change | Triggered when the status of an incident is updated. |
| Incident resolved | This incident has been resolved. |
| Incident ignored | This incident has been ignored. |
| Incident reopened | This incident has been reopened. |
| Incident regression | A new occurrence has been detected by real-time scanning of a connected source for an incident previously marked as resolved (manually or by the auto-resolver). |
| Incident Severity changed | The severity has been updated for this incident. |
| Risk score updated (Business plan) | The risk score has been updated for this incident. |
| Incident assignments | Triggered when an incident is assigned, reassigned, or unassigned. |
| Incident assigned | This incident has been assigned to a user. |
| Incident reassigned | This incident has been reassigned to a different user. |
| Incident unassigned | A user was unassigned from this incident. |
| Incident access | Triggered when a user's access to an incident changes. |
| Incident access granted | A user has been granted access to this incident. |
| Incident access revoked | Access to this incident has been revoked for a user. |
| Publicly shared | Triggered when the public sharing link of an incident changes. |
| Incident shared publicly | A user has generated a public sharing link for this incident. |
| Incident unshared publicly | A user has deactivated the public sharing link for this incident. |
| Messages | Triggered when a new message is added to an incident. |
| Feedback submitted | A feedback has been submitted for this incident. |
| New comment on an incident | A new note has been created for this incident. |
Filter notifications by incident criteria
You can define filtering rules so this notifier only sends notifications for incidents that match the criteria you choose — by severity, ML risk score, validity, secret type, or GitGuardian tags, on both internal and public monitoring incidents. If you don't set any rule, every incident is notified (the default).
See Filter notifications by incident criteria for the full list of criteria and important notes on notification timing.