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

ZA trigger

Trigger starts the Zap

Zapier trigger · New trigger event

Use the ID from this event as the Checkilo run ID.
WH checkilo ping /start

Tell Checkilo the run started

Webhooks by Zapier · Custom Request

Place this webhook immediately after the trigger.
AP action

Run the main action

Your main app · Create or update record

This is the work Checkilo is protecting.
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.

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"}

Setting up Checkilo in Zapier

Use the detailed setup map above as the source of truth for the Zap steps and fields. It shows the Webhooks by Zapier steps to create, the URL field values to paste, and how Checkilo treats each ping.

Before you start

You need:

A Checkilo account.
One check already created in Checkilo.
The check's base ping URL, such as https://ping.checkilo.app/abc123xyz9mZ.
Zapier access to Webhooks by Zapier and, for failure branches, Paths by Zapier.

Build the Zap steps

Keep your existing Zap trigger as step 1.
Add Webhooks by Zapier -> Custom Request immediately after the trigger for /start.
Add the action your Zap is supposed to perform.
Add Paths by Zapier if you want explicit success and failure outcomes.
Put the /success webhook on the success branch.
Put the /fail webhook on the failure branch and use POST if you want alert metadata.

The run query value must come from the same trigger field in every Checkilo webhook. Use Zapier's data picker instead of typing a placeholder by hand.

What the stages mean

start means this Zap execution began. Checkilo opens a run and starts the timeout clock.
success means the Zap completed the happy path. Checkilo closes the run as successful.
fail means the Zap reached an error or rejected outcome branch. Checkilo closes the run as failed and can include safe metadata in the alert.

Test the setup

Test the Zap in Zapier.
Open the check in Checkilo.
Confirm a new run appears in Recent runs.
Open the run and confirm the timeline shows start and a final success or fail.

Troubleshooting

No run appears in Checkilo. Check Zapier task history for the webhook step. A 404 usually means the slug is wrong. A 2xx means Checkilo received the ping.

The run stays in progress or becomes timed out. The Zap sent start but did not send success or fail. Check the last webhook step in Zapier.

All pings appear as separate runs. The run query value is missing or changes between steps. Use the same Zapier trigger ID on every ping in the same Zap execution.

A failure alert did not arrive. Create a channel under Channels, then open the check's Edit page and attach that channel to the check.

Next: Pre-built templates · Understanding ping URLs

Back to all articles