SC
trigger
Schedule starts the Zap
Checkilo also watches for this trigger going quiet.
Detailed setup map
Scheduled job
My job runs on a schedule, and I want to know if it stops running. Use the builder map below as your field-by-field checklist in Zapier.
/startopens one Checkilo run immediately after the Zap trigger.
/successcloses that run after the happy path finishes.
/failcloses that run as failed from an error or rejection branch.
scheduled automation
Scheduled trigger with start and success pings
-
-
WH checkilo ping /start
Tell Checkilo the run started
Place this webhook immediately after the trigger.
-
ZA delay
Optional delay or queue
Use this only if your scheduled job intentionally waits before work.
-
AP action
Run the scheduled work
This can be any recurring sync, cleanup, or report action.
-
WH checkilo ping /success
Tell Checkilo the run succeeded
Place this webhook after the final happy-path action.
Step 1 · Schedule by Zapier
Schedule starts the Zap
Checkilo also watches for this trigger going quiet.
Where this appears in Zapier
Create this as Schedule by Zapier · Every hour.
Schedule
required
Every hour
Match this cadence with the check's expected interval.
Step 2 · Webhooks by Zapier
Tell Checkilo the run started
Place this webhook immediately after the trigger.
Where this appears in Zapier
Create this as Webhooks by Zapier · Custom Request, then paste the matching Checkilo URL into the URL field.
MethodGET
Path/start
Queryrun={{trigger.id}}
Action event
required
Custom Request
Choose Webhooks by Zapier, then Custom Request.
URL
required
Paste the Checkilo start URL immediately after the Zap trigger.
Run ID
required
run={{trigger.id}}
Use the same trigger-derived value on every Checkilo ping in this Zap run.
Step 3 · Delay by Zapier
Optional delay or queue
Use this only if your scheduled job intentionally waits before work.
Where this appears in Zapier
Create this as Delay by Zapier · Delay After Queue.
No Checkilo-specific field setup is needed for this Zapier step.
Step 4 · Scheduled work app
Run the scheduled work
This can be any recurring sync, cleanup, or report action.
Where this appears in Zapier
Create this as Scheduled work app · Run scheduled update.
No Checkilo-specific field setup is needed for this Zapier step.
Step 5 · Webhooks by Zapier
Tell Checkilo the run succeeded
Place this webhook after the final happy-path action.
Where this appears in Zapier
Create this as Webhooks by Zapier · Custom Request, then paste the matching Checkilo URL into the URL field.
MethodGET
Path/success
Queryrun={{trigger.id}}
Action event
required
Custom Request
Choose Webhooks by Zapier, then Custom Request.
URL
required
Paste the success URL after the final happy-path action.
Run ID
required
run={{trigger.id}}
Use the same trigger-derived value on every Checkilo ping in this Zap run.
Scheduled job template
Use this when your Zap runs on a timer and you want an alert if it stops starting.
The detailed setup map above shows the schedule trigger, the /start webhook, the scheduled work step, and the final /success webhook.
Checkilo defaults
The Scheduled job template creates a check with:
| Setting | Value | |---|---:| | Max run duration | 300 seconds | | Grace period | 60 seconds | | Expected interval | 3600 seconds |
Edit Expected interval if your Zap does not run hourly.
Pick the expected interval
Set Expected interval to the number of seconds between scheduled runs.
| Schedule | Expected interval | |---|---:| | Every 15 minutes | 900 | | Every 30 minutes | 1800 | | Every hour | 3600 | | Every 2 hours | 7200 | | Every day | 86400 | | Every week | 604800 |
If this value is too short, Checkilo alerts too early. If it is too long, Checkilo waits longer before alerting.
Schedule-specific run IDs
For some Schedule by Zapier triggers, the available ID field may be named differently from {{trigger.id}}. Use the data picker and choose a value that stays the same for every Checkilo webhook in that scheduled run.
What alerts mean
RunTimedOut: the scheduled job started but did not finish in time.NoNewRun: the expected interval passed and no new run started.
If you get NoNewRun while the Zap is still running, check that Expected interval matches the Zap schedule.