Slack

Connect a Slack incoming webhook to receive real-time scan results, critical-finding alerts, and CVE Watch notifications. Each integration can subscribe to specific event types and filter by severity, scan type, or project so each channel only gets what its team needs.

Setup

Create a Slack incoming webhook. In Slack, go to api.slack.com/messaging/webhooks, pick the workspace and channel, and copy the webhook URL.
Add the integration in Vygl. Open Settings → Integrations, click Add Slack, paste the webhook URL.
Subscribe to events. Pick which events should fire to this channel — see the event list below.
Apply filters — restrict to specific projects, scan types, or severities. Useful when one channel cares only about production findings.
Test. Click the Test button on the integration row; a sample message should appear in your Slack channel within a few seconds.

Available events

scan_completed — every successful scan
scan_failed — engine errors or upload failures
critical_finding / high_finding — new findings at that severity
cve_critical / cve_high / cve_batch_summary — CVE Watch alerts
rule_imported — git-imported rule updates

What’s in a notification

A typical scan-completion message includes:

Project name, branch, scan types that ran, duration, trigger (push / PR / manual / scheduled), commit SHA.
Severity breakdown with emoji indicators.
All new findings with type (SAST / SCA / Secrets / IaC), rule ID, file location, and clickable links.
All recurring findings with first-seen and last-seen dates.
AI verdict (true positive / false positive / uncertain) when available.
A link to the full scan detail in Vygl.

CVE Watch messages are similar but scoped to the affected dependencies and include EPSS / KEV signals.

Disabling temporarily

Toggle the integration’s Enabled switch off to pause it without deleting the configuration. Useful for maintenance windows or noisy onboarding periods.