denis256 notes and projects

n8n [email protected] was published on June 19, 2026, with a focused fix for the Form Trigger Node. The patch adds a default value for the authentication parameter so old workflows do not crash when they are opened or run against newer node code. It is not marked as a prerelease, and the scope is narrow enough that operators should read it as a compatibility repair rather than a feature release.

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

Form Trigger Node Gets A Safer Default

The only listed bug fix in [email protected] is for the Form Trigger Node. The maintainers added a default value for the authentication parameter to prevent a crash on old workflows, tracked in issue #32629 and shipped in commit 174da99.

The important detail is the age of the workflow. A workflow created before the current authentication setting existed may not have stored a value that the newer node code expects. A missing value in that path is dull until it is not. The UI or execution path can fail before the user gets a useful hint about what field is wrong.

This patch makes the node more tolerant of that saved workflow data. That is the right kind of patch release work. It removes a sharp edge without asking users to edit every old workflow by hand.

Why This Matters For Operators

A form trigger is often a boundary between outside input and internal automation. It may receive customer intake data, internal requests, or small operational forms. When that node crashes because a saved authentication value is missing, the failure is visible to people who only care that the form worked yesterday.

For teams running long lived n8n installs, this kind of compatibility fix matters more than its size suggests. Old workflows are common. They survive version upgrades, team changes, and forgotten experiments that later become production paths. If one of those workflows uses the Form Trigger Node, [email protected] is worth noticing.

There is no new behavior called out beyond the default value. The value of the release is that old workflow definitions should be handled with less drama when the Form Trigger Node reads its authentication settings.

What Is Not In This Release

The public notes for [email protected] list one product change. They do not call out breaking changes, new CLI flags, database migrations, security patches, or deprecations. They also do not describe a required manual migration step.

That narrow scope is useful information. Operators can treat this as a small bug fix release, not as a broad workflow engine update. The generated review badge blocks in the release body are not product changes. They point to review tooling around the pull request, not to settings that users need to configure.

If you maintain self hosted n8n, the practical check is simple. Open an older workflow that uses the Form Trigger Node and confirm it still loads cleanly. If that workflow receives important form submissions, run the form path once in a safe environment before moving the update through production.

Where to get it

• Release page: GitHub release page
• Repository: project repository
• Tag: [email protected]