The n8n release [email protected], published on July 13, 2026, fixes an early webhook error path that could leave an execution promise unsettled. The patch also separates execution visibility from the sharing license feature and restores ASCII simplified property keys for earlier versions of the Notion node.
The full release notes and downloads are on the GitHub release page.
Webhook errors now settle the execution promise ¶
The main operator facing change is the webhook execution promise fix. Before this patch, an error early in webhook execution could leave that promise unsettled. The correction makes the error path complete the same asynchronous contract that callers expect from other terminal outcomes.
For webhook based ingestion, promise settlement is part of control flow, not a cosmetic implementation detail. An unsettled promise can leave surrounding request handling waiting for completion that never arrives. That can make a clear application error look more like a stalled request and can move detection toward an outer timeout.
The notes do not identify the exact early error triggers. They also do not claim changes to retry policy, response payloads, execution persistence, or webhook transport. Operators should therefore treat this as a lifecycle fix and keep existing retry and timeout assumptions until those behaviors are tested against their own workflows.
After deployment, a focused check should exercise webhooks that fail before normal workflow processing begins. Confirm that the request reaches a terminal result and that the associated execution follows the expected error path. That is more useful than a broad success case because the changed code concerns early failure settlement.
Execution visibility is independent of sharing ¶
The core now decouples execution visibility from the sharing license feature. The release notes are concise, but the boundary is important: whether executions are visible should no longer depend on whether the sharing feature is licensed.
For platform teams, this separates an operational inspection concern from a product entitlement concern. Execution records are often the first place to inspect failed input, node output, and workflow state. Tying that visibility to an unrelated sharing capability can make diagnosis depend on a license branch rather than the execution itself.
No new configuration key, migration step, or permission model change is listed for this fix. The practical validation is to compare execution access for the roles and license state already used in production. This release only states that the sharing license dependency was removed, so broader access changes should not be inferred from the note.
Earlier Notion nodes regain ASCII keys ¶
The Notion node fix restores ASCII simplified property keys on earlier node versions. This is a compatibility correction for workflows that remain pinned to those earlier versions, not a general redesign of current Notion node output.
Property key normalization affects the data contract exposed to later nodes. A workflow may select, rename, or map a field by its simplified key. If that key changes, the upstream request can succeed while downstream expressions receive a different field name. Restoring the prior ASCII form reduces that compatibility risk for the affected earlier node versions.
The release notes do not enumerate the affected properties or node versions. Teams with Notion based ingestion should test representative property names, especially names that previously passed through simplification, and compare the resulting keys with saved execution data. There is no documented schema migration in this release.