A schedule, webhook source or trigger silently stops producing runs.
Know when a workflow goes quiet — before your client does.
Give each critical n8n workflow a private heartbeat URL. We watch for missed expected runs and workflow-reported failure or low-output signals. No n8n credentials, workflow JSON or customer payloads are stored.
Green execution does not always mean healthy automation.
Your workflow can deliberately report a failed business outcome even when n8n itself stays up.
A successful-looking run that produces zero or too few records can be treated as an incident.
One small HTTP call per workflow.
- After signup, we provision a private token for each workflow.
- Add one HTTP Request node after the business outcome is known.
- Send an optional output count or explicit fail signal.
- Our hourly watchdog checks for stale or abnormal evidence and emails you when an incident appears.
No workflow payload required.
POST /functions/v1/workflow-watch-heartbeat
Content-Type: application/json
{
"token": "YOUR_PRIVATE_TOKEN",
"status": "ok",
"output_count": 42,
"execution_id": "{{$execution.id}}"
}Health evidence, not customer data.
The beta stores the monitor name, expected interval, timestamps, status, optional numeric output count and optional execution ID. Do not send workflow payloads, credentials, prompts, customer records or production secrets.
Narrow on purpose.
This is an early hosted watchdog, not a full observability platform. Checks run hourly. Alerts are email-first. The current product detects missed heartbeat windows plus workflow-reported failure and low-output signals. It does not independently verify every downstream business action.
That narrow boundary lets an agency test proactive monitoring without operating another monitoring stack.
$49/month · up to 10 workflows
Cancel anytime. After checkout, setup instructions and private monitor tokens are emailed from hello@supportkeep.com. No production login is required.
Start hosted watch