n8n guide

Add a heartbeat to an n8n workflow

An HTTP Request node at the end confirms the run actually happened. If n8n stops starting the workflow, that signal disappears and Verifagent opens an incident.

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

Setup

Copy the monitor URL

In Verifagent, open the monitor page and copy the full ping URL. Use a distinct monitor per workflow.

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

Add HTTP Request at the end

In the n8n editor, add an HTTP Request node after the last business action. Connect that action’s main output to the new node.

Configure the call

Choose Method GET, paste the URL, leave Authentication on None. No headers or body required.

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

Run the node

Click Execute step. n8n should show HTTP 200 and the JSON body returned by Verifagent.

{"ok":true}

Place the heartbeat after the last required step, not on a side branch. If several branches must all succeed, join them before the HTTP Request node.

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

Run the workflow manually, then return to its Verifagent page. Status becomes Up and the last signal shows this test’s time.

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