Native Discord alert channel
Connect a Discord channel webhook to PulseStack and every failure and recovery arrives as a clean, colour-coded embed. No bots to build, no automation platform in the middle, no context switching away from where your team already talks.
14-day free trial on every paid plan. No credit card needed for the trial or the Free plan.
🔴 Monitor DOWN
Monitor
Checkout API
Type
HTTP
Detail
Down from 2/3 locations: London, New York
Failing
London, New York
Passing
Sydney (212ms)
PulseStack™ • Today at 09:41
🟢 Monitor RECOVERED
Monitor
Checkout API
Type
HTTP
Detail
Back online (was down 6m 12s)
Passing
London (180ms), New York (95ms), Sydney (212ms)
PulseStack™ • Today at 09:47
Example. Discord shows the name and avatar you give the webhook.
8
native alert channels, Discord included
9
monitor types you can route to Discord
2-way
failure and recovery embeds
30s
fastest check interval, Pro and above
A Discord webhook is the whole integration. There is nothing to install and no bot to code. If you can copy a URL, you can wire up alerts.
In your Discord server, open the channel that should receive alerts, go to Edit Channel then Integrations then Webhooks, and create one (you need the Manage Webhooks permission). Copy the generated URL.
Open Alert Contacts, click Add contact, choose Discord and paste the URL into Webhook URL. Give it a label like on-call or ops so you know which channel it maps to.
Tick the contact under Notify on failure on each monitor that should post here. A monitor with nothing ticked alerts every contact, so you can send everything to one channel or split monitors across several.
Click Send test. A green PulseStack™ Test Alert embed should land in the channel; if Discord refuses it, the error shows the status code, for example Discord returned 404.
PulseStack formats the embed so the responder can size up the incident without leaving Discord. No raw JSON, no guesswork.
🔴 Monitor DOWN with a red side stripe, or 🟢 Monitor RECOVERED with a green one.
The name you gave the monitor, or its URL if it has no name. The URL is not a separate field.
HTTP, KEYWORD, TCP_PING, PORT, API, HEARTBEAT, SSL, DNS or DOMAIN_EXPIRY.
For multi-location monitors, how many locations failed and which. For SSL, DNS, domain expiry and heartbeat monitors, the check's own message, such as Certificate expires in 6 days.
The cities (London, New York or Sydney) whose latest check failed.
The cities still answering, each with its response time in milliseconds.
The time of the alert, which Discord shows in each reader's own time zone.
On recovery, the Detail field says Back online and how long the monitor was down.
PulseStack builds a proper Discord embed for every event. The red or green side stripe encodes state instantly, fields keep the detail scannable, and the footer carries the timestamp Discord renders in each reader's own timezone.
Because it is a native channel and not a generic relay, we control the layout. You get the same structured embed whether the trigger was an HTTP 500, a failed TLS handshake, a missing keyword or a domain about to expire.
Example: the JSON posted to your Discord webhook
{
"embeds": [
{
"title": "🔴 Monitor DOWN",
"color": 14427686,
"fields": [
{ "name": "Monitor",
"value": "Checkout API", "inline": true },
{ "name": "Type",
"value": "HTTP", "inline": true },
{ "name": "Detail",
"value": "Down from 2/3 locations: London, New York" },
{ "name": "Failing",
"value": "London, New York", "inline": true },
{ "name": "Passing",
"value": "Sydney (212ms)", "inline": false }
],
"timestamp": "2026-07-25T08:41:07.000Z",
"footer": { "text": "PulseStack™" }
}
]
}Example values; the field names, order and colours match what PulseStack™ sends. Recovery embeds are titled 🟢 Monitor RECOVERED, with the color field set to 1483594 (green).
Discord is one of eight channels PulseStack delivers to directly. Mix and match them per monitor so the right people hear about the right incidents on the platform they already use.
Zapier and Google Chat are not native channels. They connect through the Webhook channel. SMS alerts are included on Team and Enterprise plans. See all integrations.
Whatever you monitor, its alerts can land in Discord as an embed. Pick the checks that matter and point them at the channel that owns them.
Status codes, response time and content checks on any URL.
Alert when expected text appears or vanishes from a page.
TCP connection checks to any host and port, with connect time.
Confirm a specific TCP port is open and accepting connections.
Endpoint checks with custom headers and status validation.
Catch silent cron and background jobs that stop checking in.
Alert when a certificate nears expiry or turns invalid.
Alert when a record no longer holds the value you expect.
Alert when a domain registration is close to expiring.
Route production monitors to your incident channel. The embed carries enough context that the responder starts triaging before opening the dashboard.
Discord is already home. Point your game server, API and status-page monitors at a staff channel so moderators see downtime the second players would.
Give each client their own Discord server and webhook. Client sites report into channels the client can watch, without you juggling a separate tool per account.
No paid incident tooling required. Two-location confirmation plus recovery embeds turns one Discord channel into a lightweight, always-current status board.
PulseStack posts to your webhook directly. There is no automation platform to sign up for, keep running, or pay for on top. Fewer moving parts, fewer places for an alert to get lost.
Because Discord is native, the embed layout is consistent and readable every time. You are never staring at raw payload text trying to work out what broke.
Re-tests and two-location confirmation mean the channel only lights up for incidents that are real. Recovery embeds close the loop automatically.
Start with Send test next to the contact on the Alert Contacts page. It posts a green test embed straight away, and if Discord refuses it the error shows the status code Discord returned.
The form accepts URLs that start https://discord.com/api/webhooks/ or https://discordapp.com/api/webhooks/. A URL copied in the PTB or Canary app starts ptb.discord.com or canary.discord.com instead; change the start to https://discord.com and it is the same webhook.
Discord answers 404 (Unknown Webhook) once a webhook is deleted, including when its channel is deleted, and 401 when the token at the end of the URL is wrong or cut short. Create a new webhook and replace the contact.
Discord rate-limits webhooks. If lots of monitors go down or recover in the same moment, Discord can answer 429 Too Many Requests, and PulseStack™ posts each alert once without retrying, so some embeds may be missing.
If a monitor has any contacts ticked under Notify on failure, only those are alerted. Tick the Discord contact, or untick everything so the monitor alerts every contact.
Embeds are posted when a monitor goes down or recovers, not on every check, so a monitor that was already down when you added Discord posts nothing until it recovers. If an embed you did get looks wrong, see why a monitor status can be wrong.
Yes. Discord is one of PulseStack™'s eight native alert channels, alongside Email, SMS, Slack, Microsoft Teams, PagerDuty, Telegram and Webhooks. There is no third-party relay: you paste a Discord channel webhook URL into PulseStack™ and it posts to that URL directly.
In Discord, open the channel's Edit Channel settings, go to Integrations, then Webhooks, create a webhook and copy its URL (you need the Manage Webhooks permission). In PulseStack™, open Alert Contacts, click Add contact, choose Discord, paste the URL and click Send test. Then tick the contact under Notify on failure on the monitors you want to notify.
Each alert is one embed: Monitor DOWN with a red side stripe or Monitor RECOVERED with a green one, then fields for Monitor, Type and Detail, the failing cities, the passing cities with their response times, a timestamp and the footer PulseStack™.
Yes. Alerts fire on failure and again on recovery, so the channel always reflects the live state. Failed checks are re-tested and confirmed from at least two locations before a failure alert is sent, which keeps noise down.
Yes. Create a separate webhook for each Discord channel and point specific monitors at each one, so different teams see only the alerts they own.
No. The Free plan includes 5 monitors with 5-minute HTTP checks and email alerts, at no cost and with no card required. Discord alerts come with the paid plans, and every paid plan starts with a 14-day free trial with no card needed.
Wire a Discord webhook into PulseStack and start receiving structured failure and recovery embeds today. Free plan needs no card, and every paid plan opens with a 14-day free trial that needs no card either.