Checkilo

Detailed setup map

Linear flow

My flow has one main action and should close as success or failure. 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.

branching automation

Trigger, start ping, main action, success or fail ping

4 Zap steps
  1. ZA trigger

    Trigger starts the Zap

    Zapier trigger · New trigger event

    Use the ID from this event as the Checkilo run ID.

  2. WH checkilo ping /start

    Tell Checkilo the run started

    Webhooks by Zapier · Custom Request

    Place this webhook immediately after the trigger.

  3. AP action

    Run the main action

    Your main app · Create or update record

    This is the work Checkilo is protecting.

  4. PA path 2 branches

    Paths by Zapier closes the run

    Use success and failure branches so every run has a final Checkilo state.

    Success The main action completed successfully.
    WH Tell Checkilo the run succeeded /success
    Failure The main action failed or returned a rejected outcome.
    WH Tell Checkilo the run failed /fail

Step 1 · Zapier trigger

Trigger starts the Zap

Use the ID from this event as the Checkilo run ID.

Where this appears in Zapier Create this as Zapier trigger · New trigger event.
Trigger ID required
{{trigger.id}}

Pick a stable value from the trigger output and reuse it as the run ID.

Step 2 · Webhooks by Zapier

Tell Checkilo the run started

Place this webhook immediately after the trigger.

Checkilo /start
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 · Your main app

Run the main action

This is the work Checkilo is protecting.

Where this appears in Zapier Create this as Your main app · Create or update record.

No Checkilo-specific field setup is needed for this Zapier step.

Step 4 · Paths by Zapier

Paths by Zapier closes the run

Use success and failure branches so every run has a final Checkilo state.

Step 4 · Success branch · Webhooks by Zapier

Tell Checkilo the run succeeded

Place this webhook after the final happy-path action.

Checkilo /success
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.

Step 4 · Failure branch · Webhooks by Zapier

Tell Checkilo the run failed

Place this on the failure branch if the main action cannot complete.

Checkilo /fail
Where this appears in Zapier Create this as Webhooks by Zapier · Custom Request, then paste the matching Checkilo URL into the URL field.
MethodPOST Path/fail Queryrun={{trigger.id}}
Action event required
Custom Request

Choose Webhooks by Zapier, then Custom Request.

URL required

Paste the fail URL on the branch that represents an error or rejected outcome.

Run ID required
run={{trigger.id}}

Use the same trigger-derived value on every Checkilo ping in this Zap run.

Header recommended

Required when sending failure metadata in the request body.

Data recommended 
{"reason":"{{error.message}}","step":"{{zap_meta_human_now}}"}

Optional metadata helps the alert explain why this branch failed.

Failure metadata sample

{"reason":"{{error.message}}","step":"main action"}

Linear flow template

Use this when your Zap has one main path and you want Checkilo to record a clear beginning and ending for each run.

The detailed setup map above shows the Zapier steps to create and the fields to fill in. Follow it from top to bottom.

Checkilo defaults

The Linear flow template creates a check with:

| Setting | Value | |---|---:| | Max run duration | 300 seconds | | Grace period | 60 seconds | | Expected interval | blank |

Leave Expected interval blank because this template is for event-driven Zaps.

Setup notes

Put /start immediately after the trigger. Put /success after the last action that means the Zap really finished. If you add a failure path, put /fail only on the branch that represents an error or rejected outcome.

Every Checkilo webhook must use the same run value. Pick a stable trigger field in Zapier's data picker and reuse it on every Checkilo step.

Test

  1. Test the Zap in Zapier.
  2. Open the check in Checkilo.
  3. Open the new run.
  4. Confirm the timeline ends with success or failed.

If the run times out, the final success or fail ping did not arrive. Check Zapier task history for the last Webhooks by Zapier step.

Next: Multi-step with failure tracking · Understanding ping URLs

Back to all articles
Checkilo © 2026 Checkilo Help
All systems operational