Everything worth asking before you trust it.

The health layer for your business-critical automations. You add checkpoint pings to the steps that matter, and Checkilo turns them into run timelines, missing-run alerts, failure context, and automation health history.

A couple of minutes. Create a check, get its ping URL (or use the native n8n node), add it at a step, and your first run appears on the timeline.

No. Use the native n8n node, or paste a ready-made ping URL into Zapier's Webhooks step or Make's HTTP module. No curl required, no servers.

Yes. Free covers 3 monitored automations with no card. You only add billing if you upgrade to Pro.

A lightweight HTTP request your automation sends at an important step. Checkilo records the ping, decides the run's state, and fires an alert when something is missing.

An event ping fires once at the end (one-shot). A workflow ping marks the start, named checkpoints along the way, then success or fail, so you get a step-by-step timeline of each run.

Three things: a run failed, a run timed out, and no new run arrived on schedule. Each alert names the last checkpoint reached.

Yes. Anything that can send an HTTP request works: cron jobs, backend services, scripts, or your own app, not just no-code platforms.

Zapier, Make, n8n, or any tool or script that can send an HTTP request. Checkilo is a complementary layer on top of the platform that runs your automation, not a replacement for it.

There is a native Checkilo node. Pick the automation and the event inside the node; there's no manual HTTP to wire up.

Use Zapier's Webhooks step or Make's HTTP module with method POST, and paste the ping URL Checkilo gives you. The dashboard includes copy-paste examples, so non-technical users can set it up without code.

Not yet. Native Checkilo apps for Zapier and Make are coming soon, pending each platform's review. Until then, the built-in webhook step takes about two minutes. The n8n native node is already available.

Email, Slack, Discord, Telegram, LINE, Teams, and Webhook, seven channels in total, available on every plan including Free.

The automation, the last checkpoint it reached, and when it went quiet. No vague "something went wrong" messages.

Paid plans re-alert until you acknowledge, then escalate to a second channel. SMS, phone calls, and multi-step on-call rotation are coming soon on Business.

Yes. Quiet hours and maintenance windows on Pro stop expected noise without turning off monitoring.

Yes. Run timelines, alerts, and health history are on every plan. Paid plans add duration and success-rate trends, failure-step ranking, anomaly alerts, and digests.

It flags a run that is unusual against its own baseline, for example far slower than normal, even when the run technically succeeded. Available on Pro.

A summary of what Checkilo caught and how your automations trended. Free gets a monthly teaser; Pro gets a full weekly digest. Per-client breakdowns are coming soon on Business.

Free for 3 automations with no card. Pro is $19/mo for 25 automations. Business ($49/mo for 200) is coming soon. See the full breakdown on the pricing page.

One tracked execution of an automation, whether it finishes, fails, or times out. Individual checkpoint pings within a run do not count separately.

Yes. Upgrade or downgrade whenever you like; changes take effect immediately and billing is prorated.

Alert content is shown verbatim, so keep secrets and sensitive customer data out of ping payloads. Pings are meant to carry checkpoint labels and run IDs, not personal data unless you put it there.

Per plan retention: 7 days on Free and 30 days on Pro; Business (90 days) is coming soon. Older run history is removed automatically.

Yes. You can delete a check and its history at any time. CSV export and a REST API are coming soon on Business.