Hear about a broken client workflow before your client does.
We check your clients' n8n runs every 5 minutes. You get a message when one fails, stops running, or finishes with nothing. Each alert has a short note you can forward to the client. No changes to your clients' workflows.
A run goes wrong, you get a message, you tell the client first.
Example: a failed run on a client server sends you a message with a note you forward to the client.
Catch the runs that succeed but do nothing.
A workflow can finish without an error and still do nothing. The trigger found no new rows, the API sent back an empty list, or a filter dropped every item. n8n marks that run as a success, so nobody notices until the client asks where their leads went.
Pick the step that should always produce something, like the one that writes to the CRM. If a run finishes and that step produced nothing, you get a message.
Example: n8n reports success, but the Find rows step produced 0 items and Add to CRM never ran, so you get an empty run message.
Plus the usual checks
How to start
- Sign in with your email or Telegram, or open the bot and send /start.
- Open the sign-in link we email you, or the one the bot sends you.
- Add a client's n8n address and an API key. We test the connection before saving anything.
- Pick which steps to watch for empty runs.
Free for 14 days. No card needed.
- Checks every 5 minutes
- Failed, missed, empty-run and server-down alerts
- Alerts by email, Telegram or Slack
- A note to forward to your client with each alert
- 14-day money-back guarantee
- Everything in Solo
- No per-server price as you add clients
Fair use: built for client work, not for load testing.
- Alerts in a shared Slack channel.
- An onboarding call to connect your client servers, if you want one.
- More than one person signed in: we'll work out what you need with you.
Free for 14 days. Then $9 a month for up to 10 client servers, or $19 a month for unlimited servers.
14-day money-back guarantee on every payment.
Founding offer: 30% off for life with code FOUNDING30, for the first 50 customers, until 30 October.
Your clients' keys stay safe
Encrypted with AES-GCM · we only read run history · never in logs · deleted with the server
How we handle API keys →Questions
Do I need to change my clients' workflows?
No. We read run history through the n8n API. Nothing is added to or edited in any workflow.
Does it work with n8n Cloud and self-hosted n8n?
Yes, both, as long as the n8n API is turned on and the server is reachable from the internet.
How is this different from n8n's Error Workflow?
Error Workflow runs when an execution fails. It can't tell you about a schedule that never ran, or a run that finished green with 0 items. We check for all three, on every client server.
What can you do with the API key?
n8n API keys can usually do more than read. n8n lets a key create, edit and run workflows, and we can't narrow a key ourselves. We choose not to: we send GET requests only, to three endpoints. /api/v1/workflows lists the active workflows. /api/v1/executions lists recent runs, and checks that the server saves successful runs. /api/v1/executions/{id} reads one run, to count a step's items or read an error. We never create, edit, run or delete anything. The key is encrypted, never written to logs, and deleted when you remove the server. For extra safety, create it from a separate n8n user who can only see the projects you want watched.
Do I have to use Telegram?
No. You can sign in with email or Telegram, and get alerts by email, Telegram or Slack. Pick the channels you want, and send a test alert to see how it looks. Every alert email has a link to turn email alerts off.
What happens when the free 14 days end?
Alerts pause until you pick a plan. Nothing is charged automatically, because we never ask for a card up front.