n8n [email protected] - Billing Count and Security Fixes

n8n [email protected] was published on June 22, 2026, as a small patch release for workflow execution accounting and dependency security fixes. The core change for data teams is that error workflow executions are excluded from the billable execution count, which makes failure handling less likely to distort usage reporting.

The full release notes and downloads are on the GitHub release page.

The most operator visible fix is in core execution accounting. The release notes say n8n now excludes error workflow executions from the billable execution count, tracked as #32544.

That matters in production automation because error workflows are often part of the control plane around a data job. They send alerts, write audit records, route failed payloads, or open incident tasks. Counting those compensating executions as normal billable work can make a noisy failure window look like extra business workload.

For platform teams, this is mostly a reporting correctness change. It does not claim to alter retry behavior, workflow semantics, or how failed executions are stored. The useful effect is narrower: usage metrics should separate the original automation work from the workflows that run because something already failed.

The release includes two security fix entries for runtime dependencies. One fixes 21 issues across tmp, protobufjs, ws, and eight more packages, tracked as #32687. The other fixes 5 issues across tmp, ws, axios, and one more package, tracked as #32706.

The release notes do not list CVE identifiers or affected call paths. Treat this as dependency hygiene, not as a documented application exploit bulletin. For operators, the practical read is still clear. n8n instances that make outbound HTTP calls, process webhook traffic, or handle serialized payloads depend on these package families in places that deserve routine patch discipline.

The package names also map to common automation surfaces. axios is in the HTTP client path for many Node based integrations. ws is the WebSocket package many services use for live transport. tmp touches temporary file handling. protobufjs is part of binary schema processing in Node ecosystems. The release notes do not say which n8n features exercise each dependency, so do not infer a direct exposure path without checking the deployed build.

This is not a feature release for workflow authors. There are no new node capabilities listed, no schema migration notes, and no breaking change section. The value is operational: cleaner accounting during failure handling, plus a smaller known vulnerable dependency surface.

For teams using n8n as an ETL or ELT coordinator, the billing change is the more visible one. Error workflows are common around ingestion and sync jobs because downstream APIs fail, credentials expire, and payload validation breaks. If those error handlers were counted the same way as primary executions, usage dashboards could overstate real pipeline volume during incidents.

For self managed installs, the dependency updates are the standard reason to schedule the patch. The notes do not mention config changes, environment variables, or manual migration tasks. A normal patch rollout with backup, image pin check, and smoke tests around webhook, credential, and worker paths is enough based on what is published.

The release body is short and mostly internal. It does not describe database schema changes, queue behavior changes, worker scaling changes, or API compatibility changes. It also includes generated review badges that are not release content.

That narrow scope is useful. If your platform policy requires a change note for every automation runtime update, this one can be classified as a patch for accounting correctness and dependency security. The full source entry remains the GitHub release page.