Skip to content
← Guides

A Healthchecks.io alternative built for agents and no-code automations

If you live in a terminal, Healthchecks.io is excellent. If your jobs live in ChatGPT, Claude, Zapier, Make or n8n, you may want something shaped for that.

What both do

Both are heartbeat monitors: you tell the service when to expect a check-in, the job pings a URL when it runs, and you're alerted when a check-in is missing. Both support cron expressions, grace periods and start/fail signals.

Where Did It Run? is different

  • Built around outcomes, not just pings. Every check-in can carry an item count and output text. Set a minimum item count, a minimum size, or a required keyword, and runs that succeed with nothing in them raise an empty alert.
  • Plain-English schedules. "Every weekday by 9:15am" in your timezone, with a grace window — or a cron expression if you prefer.
  • Recipes for where agents actually run. Copy-paste setups for ChatGPT scheduled tasks (relaying the notification email to a ping URL), Claude Code, n8n, Zapier (Webhooks step), Make, GitHub Actions and cron.
  • The morning roll-call. One digest across every platform: ✅ what ran, ❌ what's missing, ⚠️ what came back empty.
  • Client folders on Pro, for automation agencies watching many clients' workflows.

Where Healthchecks.io may be the better fit

  • You need a large free tier (Healthchecks.io's free plan covers 20 jobs) or many more checks per dollar.
  • You want open-source software you can self-host.
  • You need integrations we don't offer yet (we support email, Slack, Discord and Telegram).

Pricing at a glance

Did It Run?: Free for 3 watches; Solo $15/month for 30 watches with every alert channel and the daily digest; Pro $39/month for 150 watches, client folders and 90-day history. Annual plans get two months free. See pricing.

Healthchecks.io lists a free plan with 20 jobs and paid plans from $20/month (as of October 2026; check their site for current pricing).

FAQ

Can I migrate my Healthchecks.io checks?

Create a watch with the same cron expression and grace, then swap the ping URL in your job. /start and /fail suffixes work the same way.

Do you support email check-ins?

Not yet. Email check-ins are coming soon. Today every check-in is an HTTP request to the watch's ping URL (with /start and /fail variants), and the keyword, minimum size and item count checks run on the request body.

Is there an API?

Watches can be created and listed via a JSON API with your session today; API keys and an MCP server for agents are on the roadmap.

Know the next time it doesn't run

Know when your AI agents and automations didn't run. Free for 3 watches.

Start free