Checkilo

Detailed setup map

Multi-step with failure tracking

My flow has steps that might fail, and I want to know where. 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

Start ping, checkpoint, then success or fail branch

6 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

    Process the incoming item

    First work app · Process incoming data

    Add a checkpoint after this if it is a meaningful handoff.

  4. WH checkilo ping /processed

    Record the processed checkpoint

    Webhooks by Zapier · Custom Request

    This label tells alerts the first major step completed.

  5. AP action

    Complete the final work action

    Second work app · Send or save result

    The next path decides whether to close as success or fail.

  6. PA path 2 branches

    Paths by Zapier chooses the outcome

    Send a final Checkilo ping from each branch.

    Success The final work action completed as expected.
    WH Tell Checkilo the run succeeded /success
    Failure The final work action returned an error or 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 · First work app

Process the incoming item

Add a checkpoint after this if it is a meaningful handoff.

Where this appears in Zapier Create this as First work app · Process incoming data.

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

Step 4 · Webhooks by Zapier

Record the processed checkpoint

This label tells alerts the first major step completed.

Checkilo /processed
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/processed Queryrun={{trigger.id}}
Action event required
Custom Request

Choose Webhooks by Zapier, then Custom Request.

URL recommended

Use a readable label after an important action so alerts can name the last checkpoint.

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

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

Step 5 · Second work app

Complete the final work action

The next path decides whether to close as success or fail.

Where this appears in Zapier Create this as Second work app · Send or save result.

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

Step 6 · Paths by Zapier

Paths by Zapier chooses the outcome

Send a final Checkilo ping from each branch.

Step 6 · 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 6 · Failure branch · Webhooks by Zapier

Tell Checkilo the run failed

Place this in the failure branch with optional metadata.

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":"final action"}

Multi-step with failure tracking template

Use this template when your Zap has more than one meaningful work step and you want alerts to say where the run stopped.

The detailed setup map above covers the exact Zapier structure:

  • Trigger
  • /start webhook
  • first work action
  • optional processed checkpoint webhook
  • second work action
  • success and failure paths

Checkilo defaults

The Multi-step with failure tracking template creates a check with:

| Setting | Value | |---|---:| | Max run duration | 600 seconds | | Grace period | 120 seconds | | Expected interval | blank |

Leave Expected interval blank unless this Zap also runs on a fixed schedule.

How to use the checkpoint

The processed checkpoint is optional, but useful. Place it after a step that represents a real handoff: data cleaned, record created, file uploaded, or message queued.

If the run later times out, Checkilo can show that processed was the last completed label, which narrows the search in Zapier task history.

Failure branch notes

Use the failure branch for outcomes that should alert immediately: rejected data, missing required fields, API errors, or a path that means the automation could not complete.

For /fail, prefer POST with a small JSON body. Include only safe context such as a record ID, a short reason, or the Zap step name. Do not send passwords, API keys, payment data, or national IDs.

Test both outcomes

  1. Test the success path. The run should end with success.
  2. Test the failure path. The run should end with failed.
  3. Confirm the failure run has metadata on the fail ping if you sent a body.
  4. Confirm at least one attached channel receives the alert.

Common mistakes

  • The failure ping uses GET, so no metadata is sent. Use POST for failure metadata.
  • The success and failure branches use different run values. Use the same trigger ID across the whole Zap execution.
  • The check has no attached channel. Create a channel and attach it from the check edit page.

Next: Scheduled job template · Configuring alerts

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