Discord integration
Alerting & Communication
Discord is where a lot of DevOps teams, indie shops, and security communities already coordinate all day, which makes it a natural place to surface external exposures the moment they appear. The FortWatch Discord integration (currently in development) will push new findings from your continuous external scans straight into the channels your team already watches — turning an exposed database or an expiring certificate into a rich, color-coded message someone sees in minutes, not a dashboard nobody opens.
Exposed Redis on 203.0.113.10:6379
Unauthenticated database reachable from the internet.
View finding & step-by-step fix →Discord + FortWatch
FortWatch connects to Discord through incoming webhooks — the same per-channel webhook URLs Discord exposes under a channel's Integrations settings — and posts findings as rich embeds. Each alert renders with a severity-colored sidebar (red for critical, orange for high, and so on), a title naming the affected asset, embed fields for the port or record involved, the scanner that found it, and a timestamp, plus a link back to the full finding in FortWatch. Because webhooks are scoped to a single channel, you create one per destination and map each FortWatch severity to the channel you want — so criticals can land in an on-call channel while lower-severity findings collect in a quieter digest channel. For teams that want @-mentions, FortWatch can include a role or user mention in the message so the right people get a real notification, not just a silent embed.
FortWatch scans
Eleven scanners watch your external attack surface around the clock — ports, certs, DNS, cloud buckets, exposed files and more.
AI triages the finding
Each issue is scored by real-world impact and packaged with the affected asset and a one-line explanation of the risk.
Delivered to Discord
The finding lands in Discord, routed by severity — so the right people see the right alert, fast.
What you'll be able to do
Everything the Discord integration will bring to your security workflow.
Real-time alerts
a new critical finding — an exposed Redis port, a public storage bucket, a subdomain takeover — posts to Discord the moment a scan detects it.
Severity routing
point criticals and highs at an on-call channel via one webhook, and send mediums and lows to a separate digest channel via another.
Role mentions on criticals
tag a @security or @oncall role so the most urgent findings trigger a real notification instead of sitting unread.
Color-coded embeds
each alert uses Discord's embed sidebar color to map directly to FortWatch severity, so the queue is scannable at a glance.
Scan-completion summaries
get a message when a scheduled scan finishes, including whether anything changed since the last run.
Scheduled digests
a daily or weekly roll-up of your external attack surface posted to one channel for async review.
What an alert looks like
Every finding arrives formatted for Discord — severity up front, the affected asset, and a one-line explanation of why it matters, with a link straight to the step-by-step fix.
- Severity-tagged and color-coded
- The exact asset and port affected
- One click to the full finding & remediation
Discord🔴 Critical · Exposed Redis on 203.0.113.10:6379\nUnauthenticated Redis is reachable from the internet — anyone can read, dump, or wipe the data and pivot to the host.\nAsset: cache-prod-1 · Scanner: Port Monitor · Detected: 2 minutes ago\n→ View finding & step-by-step fix in FortWatch
Set it up in minutes, once it lands
No agents, no infrastructure changes — just connect Discord and choose where alerts go.
When it launches, open Settings → Integrations in FortWatch and choose Discord.
In Discord, go to the target channel's Settings → Integrations → Webhooks, create a webhook, and copy its URL.
Paste the webhook URL into FortWatch and pick the default severity it should receive.
Add more webhooks for additional channels and map each severity to a destination, optionally setting a role to @-mention on criticals.
Send a test alert to confirm the embed formatting in Discord, then switch the integration on.
Why route FortWatch into Discord?
A finding only matters if someone sees it. Dashboards get checked when people remember to; Discord stays open all day. Routing FortWatch alerts into the channels your team already lives in collapses the gap between the moment something gets exposed and the moment someone starts fixing it — which is the entire point of continuous monitoring.
Frequently asked questions
Is the Discord integration available now?
Not yet — it is in active development. Add your email on this page and we will notify you the moment it ships.
Will it spam my server?
No. You decide which severities post to which channel, and lower-severity findings can be batched into a daily or weekly digest instead of pinging individually. Quiet findings stay quiet.
Do I need a Discord bot or special permissions?
No bot required — the integration uses standard incoming webhooks. You'll need the Manage Webhooks permission on the channel to create a webhook once, then FortWatch posts through that URL.
Want the Discord integration when it ships?
We'll email you the moment it goes live — no spam, just the launch.
Get notified
Secure your entire stack today
Start scanning in under 5 minutes. No credit card required. 14-day free trial included.