rootwatch alerts you when the expected confirmation from a scheduled automation is missing, and keeps every client’s automations in one dashboard. Any platform, one HTTP request.
Oficina Central · Quote delivery: we did not receive the expected completion confirmation by 08:15. Last confirmation received: yesterday at 08:02. Check the automation and the monitoring integration.
Oficina Central · Quote delivery: completion confirmation received at 08:41. The incident opened at 08:16 stays in the history.
Nothing to install, no access to grant. At the end of your workflow you add one request to rootwatch. If rootwatch is down, your client’s automation keeps running anyway — the request is the last step and the guide uses a short timeout.
202 Accepted
{"status":"accepted","duplicate":false}
One POST with the run’s state. The token is in the URL, and it’s the only thing you need to configure.
You can also send a start signal and a failure signal. With the execution_id, rootwatch links the three and never mixes up runs.
Step-by-step guide for n8n at launch. Make, Zapier and scripts follow the same contract.
The request leaves your automation, passes through rootwatch, is checked against the deadline and, if the confirmation doesn’t arrive, goes out as an alert.
An HTTP request with success, failed or started.
It only replies once the event is saved. Repeated pings are recognised and never counted twice.
The expected time, timezone and tolerance you set. A started with no completion counts as late too.
Email, Slack, Discord or Google Chat, with the client and the automation named. Anything else that breaks in the next two minutes travels in the same message, so a bad morning is one email and not fifty. When the confirmation comes back, we tell you that too.
A success signal confirms what your integration reported. It doesn’t verify that every business outcome of the automation was right. And a missing ping can mean several things: a run that never started, a failure before the last step, a delay. We don’t guess which. We say the confirmation didn’t arrive, and where to look.
| What we receive | What we say |
|---|---|
| A valid success ping for the expected run | Completion reported |
| A failure ping sent by the integration | Failure reported by the integration |
| A start ping, with no completion by the deadline | Completion late |
| No valid confirmation by the deadline | Expected confirmation not received |
| rootwatch itself without a reliable update | Status stale, never green on old data |
Your clients are folders inside your account. They don’t need an account, can’t see each other, and receive nothing you haven’t chosen to share. Each client’s status page is private by default; share it by link when you want, and revoke it when you want.
Example. The times run live to show the dashboard updating.
€49 + VAT, if applicable. For professionals only: companies and registered self-employed workers buying for their business. At sign-up you give your business or trade name, country and tax ID or VAT number. Applicable taxes are calculated and shown at checkout before you confirm. Monthly payment, monthly renewal.
Create the account, add a client, send the first ping and test the alert before turning coverage on. No calls, email support.