Pipedream guide

Add a Verifagent heartbeat to a Pipedream workflow

Pipedream workflows can stop when a connected account breaks or a step throws. A final HTTP step is your heartbeat.

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 / Axios Request. Place it after the last useful action on the success path.

Setup

Copy the monitor URL

Create a monitor for this workflow’s schedule or event rate. Prefer a Pipedream environment variable or secret for the URL.

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

Add an HTTP request at the end

In the workflow builder, add a step after the last business step. Choose HTTP / Axios Request (or HTTP Request).

Configure GET to Verifagent

Method GET, URL = your ping URL (from an env var). No auth headers required. Continue only on the success path.

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

# Node.js code step (after your work):
import { axios } from "@pipedream/platform";

await axios($, {
  method: "GET",
  url: process.env.VERIFAGENT_URL,
});

Test the workflow

Run the workflow once. The HTTP step should return 200 and {"ok":true}. Confirm Up in Verifagent.

{"ok":true}

Place the request after every required side effect. Match expected period to the Pipedream trigger; add grace for cold starts (often 5–15 minutes).

Available routes

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

Verify

A manual run creates an immediate ping. Disable the trigger temporarily to confirm Verifagent detects silence.

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