Push-only mode

How it works

Instead of us polling your instance, you import two small n8n workflows that push to WorkflowPulse over HTTPS:

• Reporter - runs every 5 minutes, checking in with instance health, your n8n version, and execution stats.
• Error Reporter - fires on any workflow error and pushes the failure to us the moment it happens.

The instance URL you enter is used only for links back into your n8n from alerts and the dashboard - we never open a connection to it.

Setup

1. In onboarding (or on the instance page), choose Push-only via Reporter workflowand enter a label and your instance’s URL.
2. Download both workflows. Each download is preconfigured with a fresh scoped ingest token - the token is embedded in the file and shown only that once, so treat the file like a credential.
3. In n8n: Workflows → Import from file, import both, and activate them.
4. Watch the onboarding screen - it flips to “First check-in received” as soon as the Reporter runs. Workflow names appear after that first check-in.

Existing Reporter installs

If you downloaded the Reporter workflow before July 7, 2026, download a fresh Reporter template from your instance’s workflow settings and replace the old workflow in n8n. The current Reporter paginates local workflow and execution reads, sends per-hour aggregates, and includes truncation and source-clock metadata so reports can label coverage accurately.

Older Reporter workflows still check in and are accepted, but their windows have lower confidence because they do not prove pagination completeness or exact hour-level buckets.

What push-only gives you

• Real-time failure alerts via the Error Reporter.
• Dead-instance detection: once your instance has demonstrated push mode, missing check-ins for more than 15 minutes opens an instance-down incident - a server that can’t check in can’t tell you it’s down, so we notice for it.
• Vulnerable-version alerts: the Reporter includes your n8n version, which we match against published advisories. (API polling can’t see the version at all - push mode is how version detection works.)
• Silence detection on the execution stats the Reporter sends, on paid plans.

Security properties

Ingest tokens are scoped to their endpoint, stored only as salted digests, and revocable per instance. Pushed error messages go through the same scrubbing as everything else - emails and secret-shaped strings are redacted before storage. See the security page for the full picture.