Your automation cannot tell you it never ran.
Job Heartbeat keeps the deadline outside your workflow. Add one success ping. If the next expected ping never arrives, you get alerted.
Free: monitor up to 10 jobs • Paid: monitor up to 100 for $7/month • No workflow credentials required
Add one final success step.
Create a check
Set how often the job should complete.
Copy the URL
Put it at the end of the successful path.
Let silence trigger the alert
If the next completion never checks in, Job Heartbeat notices.
run-your-job && curl -fsS "$JOB_HEARTBEAT_URL" >/dev/nullStart free. Pay $7/month only when you need more.
- Monitor up to 10 recurring jobs
- Email alerts
- Recovery notifications
- Any HTTP-capable workflow
- Monitor up to 100 recurring jobs
- Email alerts
- Webhook alerts
- Stripe-managed subscription billing
The missing completion.
A heartbeat is useful when the failure mode is “the expected run never completed.” That includes scheduler stalls, dead hosts, broken triggers, failed backups, expired credentials that prevent completion, and other cases where no final success signal appears.
What it does not magically know
Job Heartbeat does not inspect your business logic or decide whether an output is correct. If correctness matters, validate the result inside your workflow and send the heartbeat only after validation passes.
Minimal access. Clear job.
The core service needs the heartbeat signal—not your workflow credentials, prompts, API keys, or customer payloads.
- Platform-independent HTTP check-in
- Public security practices
- Published privacy policy and terms
- Stripe-managed subscription billing
- Live health endpoint
Start with one job.
Add Job Heartbeat to a recurring workflow you already care about.
Monitor up to 10 jobs at $0/month