What is Checkilo?

Checkilo watches your automations and tells you when one stops quietly.

You add small HTTP calls, called pings, to important points in a Zap or workflow. Checkilo records those pings as a run. If the run fails, takes too long, or a scheduled run never starts, Checkilo sends an alert to the channels you attached.

Use the marketing site at https://www.checkilo.app. Use the app at https://dashboard.checkilo.app.

The basic model

Check: one automation you want to monitor.
Ping URL: the unique URL for that check, such as https://ping.checkilo.app/abc123xyz9mZ.
Run: one execution of your automation.
Ping: one signal from your automation, such as start, success, fail, or a step label like sheet_saved.

A simple example

You have a Zap that copies new form submissions into a spreadsheet.

Create a check in Checkilo.
Copy the ping URL.
Add a start ping after the Zap trigger.
Add a sheet_saved ping after the spreadsheet step.
Add a success ping at the end.

If the Zap reaches the end, Checkilo shows a successful run:

start -> sheet_saved -> success

If the Zap starts but never reaches the end, Checkilo shows where it stopped and sends a timed-out alert.

What Checkilo can detect

A run explicitly failed because your automation sent /fail.
A run started but did not finish before Max run duration + Grace period.
A scheduled automation did not start within its Expected interval + Grace period.

What Checkilo does not do

It does not run your automation for you.
It does not replace Zapier, Make.com, n8n, or your own scripts.
It does not know about a step unless your automation sends a ping for that step.
It does not hide sensitive data that you send in ping metadata, so do not send passwords, tokens, card numbers, or national IDs.

Platform support

The current guided onboarding is Zapier-first. Make.com and n8n are marked as coming soon in the UI, but Checkilo can already receive pings from any tool that can send HTTP GET or POST requests.

Next: Create your first check · Setting up Checkilo in Zapier