Polling an API to check if something changed is wasteful. Webhooks flip the model — ProxyPass tells you when something happens, the moment it happens.
How It Works
You configure a webhook endpoint URL in your settings, and ProxyPass sends HTTP POST requests with JSON payloads to that endpoint whenever a subscribed event occurs. Every payload is signed with HMAC-SHA256 using a shared secret, so your endpoint can verify that the notification is authentic and untampered.
Five Event Types
Five event types are available, each toggled independently:
- Node Online — a node connected to the proxy
- Node Offline — a node disconnected
- New Node — a node was seen for the first time or reconnected after being removed
- Node Deleted — a node was removed by the customer
- Node Settings Changed — an API key was generated, regenerated, or deleted
Smart Debouncing
To prevent noise from unstable connections, online and offline events are debounced with a five-minute window. A node that briefly drops and reconnects does not flood your endpoint with rapid online-offline-online sequences. You get one notification that reflects the actual state after things settle.
Scenario: Automated Escalation Pipeline
You run 80 ProxyPass nodes across retail locations. You connect webhooks to your monitoring stack:
- Node Offline webhook fires → your monitoring system logs the event
- After 15 minutes offline → monitoring sends a Slack notification to the operations channel
- After 1 hour offline → monitoring creates a support ticket and assigns it to the field team
- After 4 hours offline → monitoring sends an SMS to the on-call engineer
When the node comes back online, a Node Online webhook fires. The monitoring system automatically resolves the ticket and sends a recovery notification to Slack.
The entire escalation pipeline runs without anyone checking a dashboard. Your team is notified at the right level of urgency based on how long the outage persists.
Security and Reliability
A security option lets you choose whether webhook payloads include API keys. By default, this is off — enable it only if your webhook endpoint is secured.
If your endpoint is unavailable when an event fires, ProxyPass retains the delivery in the webhook history. You can review what was sent and replay any missed webhook. Failed deliveries keep their full payload, giving you context to investigate what happened and when.
Webhooks turn ProxyPass from a tool you log into into a system that integrates with everything you already use — monitoring, alerting, ticketing, automation.