Indie teams and gaming-adjacent products already live in Discord. Wiring Stripe, Shopify, and CI each to their own Discord webhook means rotating three URLs when the channel changes.
AlertHub is the last hop: sources post once, then Discord (and Slack, Telegram, WhatsApp, Teams) share the same warning/critical stream. AlertHub detects a Discord webhook URL and sends a formatted embed, not a raw JSON dump.
How Discord delivery works
- You create an incoming webhook in Discord (channel-scoped URL).
- You paste it under the project Connections → Webhooks.
- AlertHub recognizes Discord and posts an embed: project name, level, title, description.
- Critical alerts use a red embed color; warning uses orange.
Only warning and critical leave the dashboard. Info alerts stay in the feed so #ops does not scroll away on every successful cron.
Setup (once)
- Create a project at app.thealerthub.com if you do not have one.
- In Discord: Server Settings → Integrations → Webhooks → New Webhook. Pick the channel, copy the URL.
- In AlertHub: Connections → Webhooks → paste the URL and save.
Docs: Discord destination. Then send any source (API, Shopify, GitHub Actions, email ingest).
Alert 1: CI failures in #deploys
Use a GitHub Actions failure step with ah_level: critical. Discord gets the embed; you do not maintain a second Discord Action.
Pair it with Netlify or Vercel if the host is the source of truth.
Alert 2: Store and payments in #revenue
Shopify orders and Stripe failures already have dedicated guides. Point those sources at the same project:
Discord is just another destination. Changing #revenue to a new channel is a webhook URL swap in AlertHub, not a Shopify Admin edit.
Alert 3: Split channels by using two projects — or one
AlertHub destinations are per project. Typical split:
| Project | Discord channel | Typical sources |
|---|---|---|
prod-ops | #incidents | CI, uptime, disk, critical Stripe |
prod-shop | #orders | Shopify, WooCommerce |
If you only have one community server, one project and one webhook is enough. Filter the dashboard by source when you need history.
Ideas to squeeze more value
- Do not paste the Discord URL into every SaaS. Rotate once in AlertHub.
- Keep customer Discord separate from ops. Ops webhooks belong in a staff-only channel.
- WhatsApp for the founder, Discord for the community team. Same alert, two destinations.
- Generic outbound. If you outgrow Discord, add Microsoft Teams without touching sources.
FAQ
Do I need to host a Discord bot?
No. Incoming webhooks are enough. AlertHub formats the embed.
Will every info alert hit Discord?
No. Info is dashboard-only. Raise the source to warning or critical when someone must be paged.
Can I customize the embed fields?
Title and description come from the alert (ah_title, ah_description, including {{placeholders}}). The embed wrapper (username AlertHub, color by level) is applied automatically.
Next steps
Follow the Discord setup, paste the webhook, then send a test warning from the Ingestion API.
Related: Microsoft Teams alerts · Google Chat alerts