n8n Workflow Telemetry

Implementation evidence

n8n Workflow Telemetry: from boundary to verified row

Use n8n Workflow Telemetry at a controlled application boundary, keep the event contract small, and verify a known outcome before building aggregate views.

1
Choose the outcome
Workflow completion monitoring
2
Define the contract
execution_id, workflow_name, workflow_version, trigger_type, schedule_name, and release
3
Instrument the boundary
Use separate explicit success and error branches so the HTTP Request node receives a final workflow outcome rather than an intermediate node result.
4
Verify the evidence
Exercise a known fixture, then inspect n8n_workflow_completed for one correctly typed terminal row.

Before you start

Prerequisites and boundaries

An n8n HTTP Request node placed on an explicit success or error branch
A header-auth credential containing the Telemetry API key rather than a value embedded in the workflow
A Set node that prepares only approved workflow metadata and bounded outcome fields

Delivery setup

Install and initialize server-side

Send the documented JSON shape to the Log API with a server-side key and bounded HTTP timeouts. Keep ingestion credentials out of browser bundles, client-visible environment variables, source control, logs, and exception messages.

1Prepare one reusable server-side delivery client with bounded network behavior.
2Add the outcome event at the success, failure, retry, or timeout boundary.
3Send controlled fixtures and inspect the stored rows before enabling an alert.

Snippet

Start with one structured event

Add this shape where the workflow completes, fails, or retries. Then build the dashboard from real fields.

n8n

n8n Workflow Telemetry event

json

{
  "method": "POST",
  "url": "https://api.telemetry.sh/log",
  "authentication": "predefined-header-credential",
  "timeout_ms": 2000,
  "body": {
    "table": "n8n_workflow_completed",
    "data": {
      "execution_id": "={{ $json.execution_id }}",
      "workflow_name": "={{ $json.workflow_name }}",
      "workflow_version": "={{ $json.workflow_version }}",
      "trigger_type": "={{ $json.trigger_type }}",
      "status": "={{ $json.status }}",
      "duration_ms": "={{ $json.duration_ms }}",
      "retry_count": "={{ $json.retry_count }}",
      "item_count": "={{ $json.item_count }}",
      "error_type": "={{ $json.error_type }}",
      "release": "={{ $json.release }}"
    }
  }
}

Event contract

execution_id, workflow_name, workflow_version, trigger_type, schedule_name, and release

status, duration_ms, retry_count, item_count, failed_step, and error_type

account_id, integration_name, delivery_status, environment, and region when approved

Implementation checkpoints

Checkpoint 1

Use separate explicit success and error branches so the HTTP Request node receives a final workflow outcome rather than an intermediate node result.

Checkpoint 2

Configure bounded timeouts and Continue On Fail according to whether observability delivery is allowed to affect the automation outcome.

Checkpoint 3

Do not send source-item bodies, credentials, tokens, expressions containing private data, arbitrary error messages, or full n8n execution data.

Verification

Prove the event arrived

Run this after exercising known success and failure cases. Replace the fallback table name if your final event contract differs from the snippet.

n8n-verification

n8n Workflow Telemetry verification query

sql

SELECT *
FROM n8n_workflow_completed
ORDER BY timestamp_utc DESC
LIMIT 20;

Confirm one terminal row per logical outcome, with the expected status, identifiers, units, and UTC time.

Inspect the inferred schema and verify that retries do not change field types or generate a new logical event ID.

Search the stored fields for credentials, raw payloads, prompts, private content, and unbounded error messages.

Exercise a provider timeout, ingestion rejection, and process shutdown before treating the dashboard as complete.

Implementation references

Review the event contract, data-safety guidance, and upstream primary documentation before enabling a new production path.

Event delivery and idempotency Background job monitoring Workflow correlation SQL n8n HTTP Request node n8n workflow executions

Production boundary

Keep the outcome event small and recoverable

This pattern provides

A bounded, SQL-ready outcome beside the upstream workflow.
Stable fields for dashboards, alerts, and cross-event correlation.
A fixture-driven path for validating success, failure, retry, and timeout behavior.

This pattern does not provide

An OTLP exporter, automatic collection pipeline, or replacement for detailed traces and diagnostic logs.
Exactly-once delivery merely because the payload contains an event ID.
Permission to collect raw provider payloads, user content, credentials, or regulated data.

Delivery and idempotency Batching and shutdown Troubleshoot ingestion

Event schema starting points

Review the row grain, emit boundary, required types, privacy classes, example payload, and validation checklist before adapting a query or snippet to production.

Async reliability11 fields