n8n | n8n@2.26.8

n8n n8n@2.26.8 released on 19-06-2026


n8n n8n@2.26.8 is out now. The patch prevents a crash in the Form Trigger node by adding a default value for its authentication parameter, which stops older workflows that lack the parameter from failing at runtime.

See the GitHub release for the full details, diffs and links to the commit and issue referenced in the notes.

What’s in this release

  • Form Trigger node: a default value for the authentication parameter has been added to prevent crashes on legacy workflows (issue #32629).
  • Fix implemented in commit 174da99 and published as a targeted patch release to address the runtime failure.
  • Change is backward-compatible: the default is injected so existing workflows do not require manual edits.

Upgrade notes

  • No breaking changes — the fix injects a safe default for the Form Trigger authentication parameter; still, take a routine backup of workflows and test Form Trigger-dependent flows after upgrading.
  • After updating, verify by running Form Trigger workflows that previously caused crashes and confirm there are no authentication-related errors; full release and compare links are available on GitHub.

Share any findings or regressions on the project’s issue tracker or in the comments so others know whether the fix resolved crashes in your Form Trigger workflows.

Related posts

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...

restic | v0.19.1

restic v0 19 1: safer FUSE mounts and mountpoint checks, robust backup source and exclude handling, clearer CLI JSON output, Windows SFTP deletion fixes