Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Header Auth credential value is replaced by __n8n_BLANK_VALUE_... when saving

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

  • HTTP Request nodes cannot authenticate because n8n stores an empty/invalid value
  • The only workaround is to delete the credential and create it again, hoping the bug doesn't repeat

Fix Action

Fix / Workaround

  • HTTP Request nodes cannot authenticate because n8n stores an empty/invalid value
  • The only workaround is to delete the credential and create it again, hoping the bug doesn't repeat
RAW_BUFFERClick to expand / collapse

Bug Description

When creating or editing a Header Auth credential (used in HTTP Request node), the value I enter in the "Value" field is automatically replaced by an internal n8n placeholder after saving.

Example of the replaced value: __n8n_BLANK_VALUE_e5362baf-c777-4d57-a669-6eaflf9e87f6

This happens even when:

  • The value is typed manually (not copied)
  • The value is pasted from a plain text editor
  • A brand new API key is used
  • The credential is created from the credential panel or from within a node

Observed behavior:

  1. I create a new Header Auth credential
  2. I enter a valid value (e.g., "Bearer xxx" or any string)
  3. I save the credential
  4. When I reopen it, the value has been replaced by __n8n_BLANK_VALUE_...

Impact

  • HTTP Request nodes cannot authenticate because n8n stores an empty/invalid value
  • The only workaround is to delete the credential and create it again, hoping the bug doesn't repeat

Additional context

This issue has also been reported by other users in:

To Reproduce

Steps to Reproduce

  1. Go to Credentials → Add New Credential → Header Auth
  2. Enter any name for the credential
  3. In the "Value" field, type any text (e.g., "test123")
  4. Click Save
  5. Reopen the credential
  6. Observe that the "Value" field now contains __n8n_BLANK_VALUE_... instead of your text

Expected behavior

The value should be saved exactly as entered, without any modification or replacement.

Debug Info

n8n version: Version 2.10.4 Platform: n8n Cloud Database: PostgreSQL

Operating System

Windows 11

n8n Version

Version 2.10.4

Node.js Version

22.17.0

Database

PostgreSQL

Execution mode

main (default)

Hosting

n8n cloud

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The value should be saved exactly as entered, without any modification or replacement.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING