Inactivity Monitoring

Your webhook failed 6 days ago. You just found out.

Webhooks fail silently. The provider sent the payload, your endpoint returned 200, but your handler stopped processing it three versions ago. Nobody noticed until a customer complained.

Hooklistener monitors watch your endpoints for inactivity — not just uptime. If expected webhooks stop arriving, you get an alert before your customers notice.

Hooklistener — Monitor Alerts
stripe-payments
Last webhook 4 min ago · Threshold: 60 min
Healthy
github-deploys
Last webhook 47 min ago · Threshold: 60 min
Warning
shopify-orders
Last webhook 6 days ago · Threshold: 24 hr
Alert sent to #eng-alerts and team@company.com
Alert
Recent alerts
shopify-orders · Inactivity alert6 days ago
shopify-orders · Recovered14 days ago
twilio-sms · Inactivity alert22 days ago

Know when webhooks go silent

Monitors are attached to your Debug Endpoints. Configure the threshold, pick your alert channels, and stop worrying about silent failures.

Configurable Thresholds

Set the silence window that triggers an alert — from 1 minute to 24 hours. Match the threshold to how frequently each provider sends webhooks.

Email & Slack Alerts

Get notified where your team already works. Configure one or both channels per monitor. Alerts include the endpoint name, last-seen timestamp, and threshold.

Cooldown Periods

Prevent alert fatigue. After an alert fires, the cooldown suppresses duplicate notifications for a configurable period.

Recovery Tracking

When webhooks resume, Hooklistener logs the recovery event. Full timeline: when silence started, when the alert fired, and when traffic came back.

Team Notifications

Route alerts to the right people. Send Stripe alerts to the payments team, GitHub alerts to platform eng. Not everything goes to the same channel.

Alert History

Every alert and recovery is logged. Track patterns over time — which integrations are flaky, how long outages last, and whether your thresholds need tuning.

This is not uptime monitoring

Uptime monitors ping your server to see if it responds. Inactivity monitors watch real webhook traffic to see if your integration is actually working. They catch different failures.

Uptime MonitoringInactivity Monitoring
What it watchesWhether your server responds to synthetic pingsWhether real webhook traffic is still arriving from your providers
CatchesServer crashes, DNS failures, network outagesBroken handlers, provider-side failures, silent config changes, expired API keys
Blind spotYour server is up but your Stripe handler has been silently broken for a weekNone — if webhooks stop, you know
Alert triggerEndpoint returns non-2xx or times outNo webhook received within your configured threshold
False positivesHigh — transient network blips, maintenance windowsLow — if your provider is sending and your endpoint is healthy, traffic flows

How inactivity monitors work

Monitors watch for silence, not errors. If expected webhooks stop arriving within your configured threshold, you get an alert.

1

Attach a monitor to an endpoint

Pick any Debug Endpoint and set an inactivity threshold — the window of silence that triggers an alert. Thresholds range from 1 minute to 24 hours.

2

Choose notification channels

Get alerted via Email, Slack, or both. Alerts go to the people who can actually fix the problem — not a noisy shared channel.

3

Set a cooldown period

Prevent alert spam. After an alert fires, the cooldown suppresses duplicate notifications for a configurable period so your team isn't buried in noise.

4

Track recovery automatically

When webhooks start arriving again, Hooklistener logs the recovery event. You get a full timeline: when it went silent, when the alert fired, and when it recovered.

webhook.site alternative

Graduating from webhook.site (RequestBin)? Hooklistener takes you further.

Move from one-off bins to a production-grade webhook platform with replay, forwarding, and monitoring built in. Compare features side-by-side and migrate in minutes.

Keep every payload

Persist webhook history for 14+ days, search instantly, and replay to any environment.

Forward & transform

Send events to QA, staging, and production with conditional routing and transformations.

Built for teams

Invite collaborators, mask secrets, and stay audit-ready—no public bins or shared tokens.

Comparison FAQs

Why not just use PagerDuty or Datadog?

Those tools monitor your infrastructure — servers, containers, error rates. Hooklistener monitors your webhook integrations specifically. It knows when Stripe stopped sending, not just when your CPU spiked.

Can I monitor webhooks from any provider?

Yes. Any webhook that hits your Hooklistener endpoint is monitored. Stripe, GitHub, Shopify, Twilio, or your own internal services.

Is this included in the free plan?

Monitors are available on Pro ($12/mo) and Team ($20/mo) plans. The free plan includes a Debug Endpoint with request history to get started.

Common Questions

How is this different from uptime monitoring?
Uptime monitors ping your server to check if it responds. Inactivity monitors watch for real webhook traffic — they catch silent failures where your server is up but your handler stopped processing events. Both are useful, but they catch different problems.
What threshold should I set?
It depends on how frequently your provider sends webhooks. For Stripe (which sends on every payment), 60 minutes is reasonable. For a nightly batch job, 24 hours makes sense. Start with the interval you'd expect between webhooks, then add some buffer.
How do I avoid alert spam?
Each monitor has a configurable cooldown period. After an alert fires, Hooklistener suppresses duplicate alerts for that window. You get one notification, not one per minute.
Which notification channels are supported?
Email and Slack. Configure one or both per monitor. Alerts go to the specific people or channels you choose — not a firehose.
Does the monitor track recovery?
Yes. When webhooks start arriving again after an alert, Hooklistener logs the recovery event. You get a full timeline: when silence started, when the alert fired, and when traffic resumed.
Is inactivity monitoring included in the free plan?
Monitors are available on Pro and Team plans. The free plan includes 1 Debug Endpoint with request history — upgrade when you need inactivity alerts, longer retention, or team collaboration.
Ready to start?

Start debugging webhooks
in under a minute

Create your first Debug Endpoint, set up a Monitor, or tunnel webhooks to localhost. The complete webhook toolkit is ready when you are.

Start free and upgrade for up to 60 days of history, CLI access, and more. No credit card required.

Debug Endpoints
Monitors
Email Inboxes
CLI