Make guide

Add a heartbeat to a Make scenario

The last module in the scenario calls Verifagent. As long as Make runs the scenario on schedule, the monitor stays up.

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 : HTTP · Make a request. Place it after the last useful action on the success path.

Open your monitor in Verifagent and copy its URL. The embedded token identifies this scenario only.

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

In the Scenario Builder, click the last module, add HTTP, then choose Make a request.

Use Method GET. Paste the URL. Leave Headers, Query string and Body empty.

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

Click Run once then trigger the scenario. The HTTP module bubble should show a successful run with status 200.

{"ok":true}

Keep the module on the main path, after important writes or syncs. A ping placed too early would confirm an incomplete 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

After Run once, open the monitor in Verifagent. Status switches to Up. Then confirm the Make schedule is enabled.

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