Slack
Post findings into a channel through an incoming webhook.
Choose which events post — scan failures, critical and high findings, or clean completions.
Integrations
Findings, where your team already works
Every integration subscribes to the events you choose — scan failures, critical and high findings, or clean completions — so alerting stays useful instead of noisy.
Seven ways to receive findings
Add as many as you need — each one has its own event subscription and can be tested before you rely on it.
Microsoft Teams
Deliver an adaptive card into a Teams channel.
Severity counts and the affected service are visible without opening the report.
Google Chat
Send scan results into a Chat space.
Same event filters as every other channel, configured per integration.
PagerDuty
Trigger an incident and resolve it automatically.
A1 Cloud Guard opens an incident on failure or critical findings, then resolves it when a later scan comes back clean.
Jira
Open an issue and close it when the finding clears.
Supports API token or personal access token, a chosen project and issue type, and an optional resolve transition.
Custom webhook
POST or PUT signed JSON to your own endpoint.
Payloads carry an HMAC-SHA256 signature. Add up to ten custom headers for gateways and bearer tokens — stored encrypted, never returned to the browser.
Email / SMTP
Send alerts and full PDF reports to any mailbox.
Bring your own SMTP server; credentials are encrypted at rest and the connection is tested before it is saved.
Built for endpoints behind a gateway
Webhook, Slack, Teams and Google Chat channels accept up to ten custom request headers, so an endpoint behind an API gateway or bearer-token proxy is reachable. Header values are encrypted at rest and never returned to the browser. Reserved headers are rejected, and payloads carry an HMAC-SHA256 signature you can verify.
Wire up your first alert
Add an integration in under a minute and send a test message before you rely on it.