n8n Adds Native OpenTelemetry Tracing for Workflow and Node-Level Visibility
n8n has introduced native OpenTelemetry support, giving teams end-to-end traces of workflow runs and optional visibility into individual nodes.
n8n has introduced native OpenTelemetry tracing for its automation platform, giving teams a way to follow workflow executions from their trigger through downstream actions. Announced on June 8, 2026, the capability can emit a trace for every workflow run and, optionally, a child trace span for every node. That provides a production-focused view of automations that connect services such as CRMs, payment systems, API gateways, and AI agents.
The update matters because workflow failures are often difficult to isolate once an automation crosses several applications. A failed run may be caused by a slow external API, an incorrectly mapped data field, a payment event, or a later step in a process. With OpenTelemetry, n8n can send execution data to a compatible observability backend, so teams can investigate workflow behavior alongside the rest of their software stack. The details are set out in n8n's official OpenTelemetry tracing announcement.
What native OpenTelemetry support changes in n8n
OpenTelemetry is an open standard for collecting telemetry data, including traces. In this case, n8n uses tracing to represent the path of a workflow execution. Each run produces a root span, which acts as the top-level record for the execution. Users can also enable child spans for individual workflow nodes.
That distinction is important. A workflow-level trace can show whether a process completed and how long the complete execution took. Node-level spans add diagnostic detail by showing where time was spent and where an error occurred. Rather than treating an automation as a single opaque task, teams can examine its component actions in a centralized tracing tool.
The announcement describes exports to OTLP-compatible collectors and backends, including:
- Jaeger
- Tempo
- Datadog
- Honeycomb
- New Relic
- Grafana Cloud
This interoperability is a significant part of the release. n8n users with an existing OpenTelemetry-compatible observability setup can use that environment for workflow traces rather than adopting a separate, proprietary monitoring layer. The capability applies across n8n workflows and is designed for both self-hosted and cloud deployments.
Workflow-level and node-level trace data
| Tracing level | What n8n emits | Practical use |
|---|---|---|
| Workflow execution | A root span for every workflow execution | Follow the end-to-end path, status, and timing of an automation run. |
| Individual nodes | Optional child spans for each workflow node | Identify the specific step that is slow or producing an error. |
The two levels are complementary. A root span establishes the broad execution path, while node spans help explain the outcome. For a workflow that receives a customer request, checks a database, updates a CRM, and sends a response, node-level tracing can reveal which action created a delay or failure.
Configuration and contextual attributes
n8n documents configuration through Settings > OpenTelemetry. The documentation also covers trace export and custom span attributes that can be applied at the project, workflow, and node levels. Those attributes are made available in the connected observability backend.
Custom attributes give teams a way to add relevant context to traces. Depending on how a workflow is organized, that can make it easier to filter and investigate executions by project, workflow, or the step that requires attention. The feature is therefore more than a basic execution log. It creates trace data that can be queried and viewed within tools built for operational investigation.
Why the update is useful for businesses running automations
For businesses that depend on n8n to move data between applications, an automation is part of an operational process, not simply a background convenience. Delays or errors can affect lead handling, customer communications, payment-related processes, and internal data updates. Native tracing can shorten the path from noticing a problem to locating the affected workflow step.
The strongest practical benefit is faster incident diagnosis. A team can use the trace to see the complete call path and then narrow its investigation to the node that failed or performed slowly. This is especially useful where multiple systems are involved and each system has its own monitoring data.
The release can also support more informed performance work. End-to-end traces make it possible to see where execution time accumulates, rather than assuming that n8n itself is the source of a delay. If an external service call is the slowest point in a workflow, the trace should make that relationship visible in the chosen backend.
For smaller teams, the ability to use an existing OTLP-compatible backend may reduce the friction of adding workflow observability. The value will depend on whether the business already operates compatible tooling and on how critical its workflows are. The supplied announcement focuses on tracing capabilities and configuration, rather than setting out separate pricing terms for the feature.
If n8n workflows support customer-facing or time-sensitive processes, Scalevise can help turn them into more dependable operations through production-ready n8n workflow setup. We can connect business applications, design error handling and monitoring around critical workflow paths, and reduce the manual effort needed to diagnose failures. This helps teams retain the speed of automation while gaining clearer operational control. Discuss your n8n automation project with Scalevise.
Frequently Asked Questions
What is n8n's new OpenTelemetry capability?
n8n can emit OpenTelemetry traces for every workflow execution, with an option to emit child spans for individual nodes. The traces show execution paths, timing, and status in a compatible observability backend.
Which observability backends can receive n8n traces?
n8n states that its traces can be exported to OTLP-compatible collectors and backends, including Jaeger, Tempo, Datadog, Honeycomb, New Relic, and Grafana Cloud.
How do users enable OpenTelemetry tracing in n8n?
The n8n documentation describes configuration through Settings > OpenTelemetry. It also covers trace export and custom span attributes at the project, workflow, and node levels.
Can tracing identify a failing n8n workflow node?
Yes. When node-level child spans are enabled, teams can inspect individual workflow steps to identify the node that is slow or producing an error.
Conclusion
n8n's native OpenTelemetry support brings workflow execution data into standard observability systems. By pairing a trace for each automation run with optional node-level detail, the release gives teams a clearer way to investigate failures and performance issues across connected business systems.