MONITORING LAYER / BUILT FOR n8n
Your automations shouldn’t
fail in silence.
Monitor your n8n workflows, detect missed heartbeats, and know when something needs attention before your client does.
OVERVIEW / WORKFLOWS
Every workflow. One clear view.
| Workflow | Client | Last heartbeat | Expected interval | Health |
|---|---|---|---|---|
| Lead Intake | Acme Dental | 09:14 | 5 minutes | Healthy |
| CRM Sync | Northstar Roofing | 09:12 | 15 minutes | Healthy |
| Client Reporting | Apex Logistics | 08:55 | 15 minutes | Warning · overdue |
| Invoice Automation | Acme Dental | 09:05 | 5 minutes | Critical · incident |
| Daily Inventory Sync | Apex Logistics | 08:00 | 24 hours | Healthy |
THE PROBLEM
Stop finding out from your clients.
A workflow can stop quietly. A missed sync, an empty report, a lead that never reaches the CRM. Often, the first alert is a message from your client.
Argin watches the check-ins your workflows should be sending, so silence becomes something you can see and act on.
Illustrative timing. Your configured intervals and grace windows determine health.
Invoice Automation
Heartbeat overdue
- Client
- Acme Dental
- Opened
- 09:15
- Expected interval
- 5 minutes
- Last success
- 09:05
Heartbeat overdue incident opened
Acknowledged by the team
Assigned for investigation
Workflow context, response, and recovery in one record.
INCIDENTS
Argin does the watching. You handle the fix.
When a monitoring condition needs attention, Argin records the incident and brings the workflow context into view.
Acknowledge it, assign someone to investigate, and follow the recovery. Configured email and Slack alerts keep the team in the loop.
THE HEARTBEAT LIFECYCLE
Know what happened — and when.
From the last check-in to the next recovery, keep the sequence in view.
Healthy
Heartbeat received
Healthy
Heartbeat received
Expected
No heartbeat
Overdue
Warning threshold passed
Incident opened
Critical threshold passed
Recovered
Heartbeat received
Illustrative lifecycle with a 5-minute interval. Detection occurs when health is evaluated after the configured grace threshold.
SETUP
Monitoring in three steps.
Connect the workflow you already run to a monitoring layer built around its activity.
- 01
Register workflow
Give it a name, set its expected interval, and choose the grace windows that fit the workflow.
Start with a workflow - 02 / CONNECT n8n
Add heartbeat request to n8n
Add an HTTP Request node and paste the ingest URL generated in Argin.
POSThttps://www.argin.app/api/v1/events/<workflow-token>{ "executionId": "run-12345", "status": "success" }Example only. Replace the placeholder with your generated URL. Send success and failure events from the corresponding paths.
- 03
Argin monitors activity
Heartbeats inform health. Missed intervals surface attention states, incidents, and configured notifications.
Ready for the next heartbeat
FOR AGENCIES
Built for people responsible for more than one workflow.
One client is a workflow. A growing roster is an operation. Keep the context together as the responsibility grows.
- Organize workflows by client
- See which clients need attention
- Review workflow health and incidents
- Generate client-facing health reports
2 workflows
1 workflow
2 workflows
Acme Dental
Workflow health snapshot
PDF download and report email supported
NOTIFICATIONS
When something changes, your team knows.
Connect incident visibility to the places your team already checks. Email and Slack notifications follow your plan and notification settings.
CAPABILITY INDEX
A clearer view of your operation.
- 01Workflow monitoring
- 02Heartbeat ingestion
- 03Incident history
- 04Email notifications
- 05Slack notifications
- 06Client management
- 07Health analytics
- 08Client reports
FAQ
A few good questions.
What Argin watches, how it works, and where it fits into your workflow.
Read all frequently asked questionsKnow before your
client does.
Give your n8n workflows a monitoring layer built for the people responsible for keeping them running.
Start monitoring
