How the Webhook Dispatcher Works for Livestreams on StreamKite

If you’ve ever found out a stream crashed hours after it happened — because a viewer mentioned it, or because you just happened to check your dashboard — webhooks fix exactly that gap. Instead of you having to go looking for problems, the webhook dispatcher pushes a message out the moment something happens to one of your streams: it started, it stopped, it crashed, or your plan’s about to expire. That message lands wherever you tell it to, in real time.

What a webhook actually is, in plain terms

A webhook is just a URL that your stream sends a small message to whenever something specific happens. You’re not polling anything, you’re not checking a dashboard — the event pushes itself to you. Most chat tools (Discord, Slack) and automation platforms (Zapier, Make, n8n) accept webhook URLs and can turn that incoming message into a notification, a logged entry, or a trigger for something else entirely.

Where to set it up: the Automation tab

Open the Power panel and go to the Automation tab — the webhook configuration sits below the auto-recovery and chaining sections. You’ll see a single URL field and four checkboxes for the events you want to be notified about.

Setting up your webhook, step by step

1. Get a webhook URL from wherever you want the alert to land. Discord and Slack both let you generate one from a channel’s integration settings in a couple of clicks. If you’re using Zapier or a similar tool, it’ll give you a “catch hook” URL to paste in instead.
2. Paste that URL into the webhook field in the Automation tab.
3. Tick the events you actually want to be notified about — Start, Stop, Crash, and Expiry warnings are all available individually, so you’re not forced into getting pinged for every single thing.
4. Click Save. Your settings are stored immediately.
5. Send a test. There’s a dedicated test button that fires a sample event straight to your URL so you can confirm it actually arrived before relying on it.

The four events you can subscribe to

• Stream started — fires the moment a slot’s status flips to running.
• Stream stopped — fires when a slot stops normally (not from a crash).
• Stream crashed — fires specifically when a slot goes down unexpectedly, which is usually the one people care about most.
• Expiry warning — fires once when your plan is nearing its renewal date, so you’re not caught off guard by a lapse.

Each one has its own toggle, so a setup focused purely on catching outages might only tick Crash and leave the rest off — there’s no requirement to subscribe to everything at once.

What’s actually inside the message that gets sent

Every webhook payload includes which event fired, a timestamp, a masked version of your PassKey for identification, and the relevant slot details — like the slot’s name and ID. If it’s a crash or stop event, you’ll know exactly which stream it was without having to guess from a generic “something happened” message.

Why this matters more than it seems

The gap between “a stream crashes” and “you find out about it” is where most of the damage happens — dead air on a channel for hours is worse for viewer trust and platform algorithms than the crash itself. A webhook closes that gap down to seconds. If it’s pointed at a Discord channel you already have open, or a Slack channel your team checks constantly, you find out about a problem while it’s still fresh instead of stumbling onto it later.

Combining webhooks with automation

Webhooks pair naturally with the other automation features. If you’ve got auto-recovery enabled on a slot, you’ll get a webhook the moment it crashes — and then see in your dashboard whether the recovery attempt succeeded. If you’ve got chain rules set up, a stop event webhook can double as your signal that a handoff to the next stream is about to happen. None of these features depend on each other, but running them together gives you both the automatic fix and the notification that something needed fixing.

A quick setup checklist

1. Generate a webhook URL from Discord, Slack, or your automation tool of choice.
2. Paste it into the Automation tab’s webhook field.
3. Tick at minimum the Crash event — this is the one that matters most for catching real problems.
4. Send a test and confirm it actually shows up.
5. Add Start, Stop, or Expiry if you want broader visibility, not just problem alerts.

Frequently asked questions

Do I need to know how to code to use this?
No. Pasting a Discord or Slack webhook URL requires no coding at all. Coding only comes into play if you want to build custom automation with a tool like Zapier or your own server.

Will I get spammed with notifications?
Only for the events you’ve actually ticked, and only when they happen. A stable stream that never crashes and rarely restarts will barely trigger anything.

Can I use more than one webhook URL at once?
The dispatcher is built around a single URL at a time. If you need alerts in multiple places, a common workaround is pointing the webhook at an automation tool like Zapier or Make, which can then fan the same event out to several destinations.

What happens if my webhook URL stops working?
The dispatch attempt simply fails silently on that side — it won’t affect your stream itself. Use the test button periodically, especially after changing anything on the receiving end, to confirm it’s still reachable.

The short version

The webhook dispatcher turns stream problems from something you find out about eventually into something you find out about immediately. Pick your events, paste a URL, send a test, and you’ll know about a crash the moment it happens — not the moment someone tells you.