⚡ ZERO-SETUP WEBHOOK SENTINEL FOR AGENCIES
Cronus checks the Shopify webhooks, form handlers and APIs your agency looks after every 5 minutes. When one fails, it checks again 20 seconds later. If it fails twice, an incident card goes to your Telegram or Slack channel with the status code and what to look at first.
No card. No code to install. You send the URLs, we set it up.
orders-webhook · ridgeline
POST https://api.ridgeline.co/hooks/orders
🔴 CRONUS SIGNAL · INCIDENT
Telegram
STATUS 500 Internal Server Error LATENCY 1,284 ms (budget 3,000 ms) FAILURES 2 consecutive TIME 03:10:20 UTC
First check: pull the app logs for 03:10 UTC and review the last deploy.
Works with any HTTP endpoint, including:
When a store’s webhook receiver starts returning errors, Shopify retries the delivery up to 8 times over 4 hours. If it is still failing, Shopify removes the webhook subscription. New orders stop reaching the ERP or warehouse system, and the storefront looks completely normal the whole time.
Cronus raises the alarm within minutes of the first confirmed failure, while the retries are still running and the subscription can still be saved.
Retries are spread over the four hours; the dots show the count, not exact timings.
Four mechanics, no black box. These are the same rules the engine runs on.
A failed check is repeated 20 seconds later. Only a second failure opens an incident, so a single dropped packet or a slow deploy restart doesn’t page anyone. While an incident stays open, duplicate alerts are held back.
Every endpoint is checked in parallel every 5 minutes, from outside your stack. No database access, no agent.
interval: 300s · timeout: 3s default
Each alert carries the real HTTP response and a first check to match it.
Incident and recovery cards go straight into the Telegram or Slack channel your developers already have open, one channel per client so nobody has to work out whose site it is.
Start with three endpoints for 14 days. If Cronus catches something you’d have missed, move up to 25 endpoints. No seats, no per-client fees.
Pro Agency
$99/ month
No. Cronus sends ordinary HTTP requests to the URLs you give it, from outside your infrastructure, the same way a customer or Shopify would. There’s nothing to install and no credentials to share.
Most one-off failures are a blip: a dropped connection, a container restarting during a deploy. When a check fails, Cronus waits 20 seconds and checks again. Only if the second check also fails does it open an incident and send the alert. That cuts out most false alarms; it can’t promise none, because an endpoint that is down for exactly those 20 seconds will still be reported.
We send you a summary of everything the pilot checked and caught. If you want to keep it, you move to Pro Agency at $99 a month. If not, we switch the monitors off. No card is taken during the pilot, so there’s nothing to cancel and no surprise charge.
Your part takes about a minute: email us the URLs and the Telegram group or Slack channel for alerts. We configure the monitors and send a test alert so you can see one arrive before anything real happens.
The button opens an email with everything we need already laid out.