Zapier guide

Add a heartbeat to a Zap

A final Webhooks by Zapier action confirms each complete run. If the trigger or account stops working, Verifagent detects the missing signal.

Before you start

Create a monitor with your workflow’s real frequency, then copy its URL from the dashboard. Its token is secret: do not publish it.

Module to use : Webhooks by Zapier · GET. Place it after the last useful action on the success path.

From the Verifagent monitor page, copy the full URL. Do not reuse the same token across Zaps.

https://verifagent.com/api/ping/your-ping-token

In the Zap editor, add an action after the last business step. Search for Webhooks by Zapier.

Select GET, paste the URL, leave query parameters empty. No payload required.

GET https://verifagent.com/api/ping/your-ping-token

Use Test step. Zapier should receive status 200. Then publish the Zap: a draft produces no heartbeat.

{"ok":true}

The webhook must be the last action on the main path. With Paths, add a heartbeat on every path that counts as a successful run.

The base URL is enough for a heartbeat. Variants enrich history if your platform has several branches.

GET https://YOUR_PING_URL

POST https://YOUR_PING_URL/success

POST https://YOUR_PING_URL/fail?msg=Error

The Zapier test creates a ping immediately. Confirm Up in Verifagent, then verify the published Zap is on.

Expected response: 200 {"ok":true}. The monitor moves from Pending to Up.