Webhooks for Pterodactyl

Webhooks connects your panel with everything else, in both directions.

Outgoing: server started or stopped, created, suspended or deleted, backups finished or failed, logins, password changes and more. Sent as signed JSON to your own scripts, or straight to Discord, Slack, Teams, Telegram, WhatsApp and a few others.

Incoming: secret URLs that other services can call to do one thing on the panel. Restart a server after a git push, start it when Uptime Kuma reports it down, make a backup from n8n.

What people use it for

• Firewall / router automation: every server payload includes the node, IP and all ports. Open the ports when a server starts, close them when it stops or gets deleted.
• Notifications in Discord, Slack, Teams, Telegram, WhatsApp, ntfy or Gotify
• Deployments: push to GitHub, Gitea or Forgejo and the server restarts or runs a command
• Self-healing: your monitoring reports a server down, the panel starts it again
• Backups: get told when a backup is done and pull it right away, or trigger backups from your automation
• Audit log of logins, password and email changes, API keys and 2FA

Outgoing

• Any number of endpoints, each with its own URL, format and events
• 30+ events: server lifecycle, power, backups, server settings, files, console, logins and account changes
• Signed JSON (HMAC SHA-256)
• Ready-made formats: Discord, Slack (also Mattermost / Rocket.Chat), Microsoft Teams, Google Chat, Telegram, WhatsApp (via CallMeBot), ntfy, Gotify and Apprise (100+ more services)
• Automatic retries after 1, 2, 5, 15 and 30 minutes and a "Send test" button

Incoming

• Actions: start, stop, restart, kill, console command, backup, reinstall, suspend, unsuspend, run schedule
• Each URL does exactly one action on the servers you picked, nothing in the request can change that
• Checks: GitHub / Gitea / Forgejo signature, HMAC, shared secret header, IP allowlist, cooldown
• Conditions on request fields, e.g. only for pushes to main or only when a monitor is down
• Every action shows up in the server's activity log

Also

• Clear settings page with Outgoing / Incoming / Log tabs
• Log of every delivery and every incoming call, with filters
• No core files are modified

Requirements

• Pterodactyl Panel 1.15.x
• Blueprint (beta-2026-08 or newer)
• PHP 8.2+

Installation

1. Upload webhooks.blueprint to /var/www/pterodactyl
2. Run blueprint -install webhooks
3. Open Admin > Extensions > Webhooks

Good to know

• Outgoing events are collected once a minute. Things Wings reports itself (like a finished backup) arrive in batches every 60 seconds, so those can take up to about two minutes.
• Server crashes can't be detected yet, Wings doesn't report them to the panel.

Support

Full documentation is included in the download (README.md), including how to verify signatures and set up GitHub and Uptime Kuma. If something doesn't work, send me the output of php artisan webhooks:dispatch or the message from the log.