← Back to all sparks
N

n8n

MKT AUTO
Velocity5.0

Workflow automation platform with fair-code license

n8n's patch stream is now mostly AI-builder work wearing bug-fix labels

workflow-automationai-builderself-hostedcredentialstrigger-reliabilitypatch-cadence
Current state
n8n releases patch versions every few days across several concurrent lines, with generated notes that are almost entirely a Bug Fixes list. The 2.36 and 2.37 lines have been infrastructure and credential work — proxy environment variables applied across processes, domain-restricted credentials fixed and backported, execution ids threaded through dynamic-credential storage, glibc staged into the distroless runner image. The current 2.38.1 release is far larger, and its body hits the 8,000-character storage ceiling.
Where it's heading
Read past the Bug Fixes heading and the centre of gravity has moved to the AI builder: tool call events emitted for Workflow, HTTP Request and Code tools, several tools from one provider addable through the UI, agent artifacts in the preview tab bar, managed credits preserved while building, and a requirement that a model be configured before the assistant accepts a prompt. Alongside it, trigger reliability keeps being hardened — Gmail no longer loses queued messages mid-poll or misses email when more than a hundred arrive between polls.
Prediction
The credits and model-configuration items point at metering and guardrails around the AI builder rather than at its capabilities, so expect the next releases to keep filling in how agent usage is accounted for before new agent features land.

Recent moves

  1. 1d ago

    2.38.1: AI-builder tool events, credits handling, Gmail trigger reliability

    A large release filed almost entirely under Bug Fixes. The substance is AI-builder work — tool call events for Workflow, HTTP Request and Code tools, multiple same-provider tools addable via the UI, managed credits preserved during builds, and a configured model now required before the assistant accepts a prompt — plus real trigger fixes where the Gmail trigger previously lost queued messages on a failed poll or missed email above a hundred between polls. The stored body stops at the 8,000-character ceiling partway through the Features section, so this is a floor on what shipped.

    View source ↗
  2. 2d ago

    2.37.6: execution id threaded through dynamic-credential storage

    Execution id threaded through dynamic-credential storage. Credential plumbing of the kind that fills the 2.37 line between larger releases.

    View source ↗
  3. 2d ago

    2.36.9: proxy environment variables applied across all processes

    Proxy environment variables applied across all processes — a fix self-hosted operators behind a corporate proxy would have felt immediately.

    View source ↗
  4. 5d ago

    2.37.4: domain-restricted credentials work inside their own node

    Domain-restricted credentials made to work inside their own node. Backported to the 2.36 line the same week, which is how this project services parallel versions.

    View source ↗
  5. 5d ago

    2.36.8: same domain-restricted credential fix, backported

    The 2.36 backport of that same domain-restricted credential fix. It duplicates the 2.37 release rather than carrying separate work.

    View source ↗
  6. 6d ago

    2.37.3: glibc and libatomic staged into the distroless runner image

    glibc and libatomic staged into the distroless runner image. Container plumbing for the task-runner architecture.

    View source ↗