n8n 2.47.5 blocks Public API edits to read-only credential nodes

n8n has released version 2.47.5, a maintenance update published on November 12, 2026. The release contains two bug fixes, one for the Public API and one for the workflow editor.

The main change affects the Public API. After this update, the API rejects requests that try to edit credential nodes marked as read-only. Before the fix, an API client could attempt to change those nodes, which the editor itself does not allow. The second fix is cosmetic: it aligns the corners of node borders during animation in the editor so they render consistently.

The release is small, and the release notes list no new features.

Why it matters

Read-only credential nodes are often set up to protect shared authentication settings. If the API allowed edits to them, automated scripts or integrations could change those settings without the same safeguards the editor enforces. Closing that gap keeps the API and the editor consistent. Teams that rely on the Public API for automation will benefit most from this change.

What to do

Teams that automate credential updates through the Public API should test those scripts on a staging instance before upgrading production. Anyone who expects to edit read-only credential nodes through the API should plan a different approach. For details on exact behavior and any other changes, check the release notes or confirm with n8n on its official site.