n8n 2.26.8 - Form Trigger Authentication Crash Fix

n8n [email protected] was published on June 19, 2026 with a focused fix for the Form Trigger Node. The release adds a default value for the authentication parameter so old workflows do not crash when they hit that missing value. It is not marked as a prerelease.

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

The only code change called out in this release is the Form Trigger Node bug fix tracked in #32629 and implemented in 174da99. The release notes say the node now has a default value for its authentication parameter. That is small in diff size, but it matters when old workflow definitions are still present in a production n8n instance.

For data teams, the risk is not the form UI itself. The risk is a webhook style ingress point that feeds a workflow used for routing, enrichment, approval capture, or a downstream ETL job. If an older workflow can crash because one parameter is absent, then the failure mode is a runtime surprise instead of a planned migration. This release moves that path toward a predictable default.

n8n is often used as glue around systems that do not share one clean event model. A Form Trigger can sit at the edge of a process that later calls APIs, stores rows, emits messages, or schedules follow up work. A crash at that first step can look like missing submissions, delayed sync work, or a silent break in a manual data intake path.

The fix is specifically about old workflows. That wording is important. It points to a backward compatibility issue in serialized workflow configuration rather than a new Form Trigger capability. Operators who keep long lived n8n instances should read this as a patch for existing definitions, not as a feature release that changes how authentication should be designed.

There is no broad migration note in the release notes. There is also no claim of a schema rewrite, credential model change, or queue behavior change. Treat the release as a narrow crash fix and verify the same way: run a representative old Form Trigger workflow before and after the update, with the same authentication settings and the same inbound payload shape.

This tag does not bundle a long list of node updates, worker changes, or database migrations. The public notes identify one bug fix. That makes the operational review simpler, but not optional. Small releases can still matter when they touch workflow startup or trigger evaluation.

The main item to check is whether any old Form Trigger workflows were being held back because of the authentication parameter crash. If so, [email protected] is the tag that carries the default value fix. If not, this release is still a low noise patch in the 2.26 line, with the normal caution that any automation platform upgrade should be tested against real workflow exports.

The GitHub release page includes the complete note and linked commit. It is the better source for exact provenance than a changelog summary copied into deployment tickets.