Critical Bug: Cannot Save Credential Value in n8n.io Account

Questions
,
1

Hello,

I am experiencing a critical bug where I am unable to save a ‘Header Auth’ credential value in my n8n.io cloud account. No matter what I do, the value always reverts to a blank placeholder (_n8n_BLANK_VALUE…) after I click “Save”.

This has completely blocked my workflows. I have already performed extensive troubleshooting, including:

Generating a brand new, valid Access Token directly from the Meta API dashboard.

Creating multiple new credentials from scratch (the latest one was named ‘daisa_final’).

Confirming the token format is correct (‘Bearer ’).

Testing in different web browsers.

Testing in incognito/private mode.

Clearing my browser cache.

Can someone please help me?

2

Hey @Minimal_Feature,

welcome to the community :waving_hand:t2:.

I just did a quick test on my cloud instance, running n8n v1.112.6 by creating a webhook trigger that uses header auth and all seems fine.
Can you add some more details about what are you trying to do?

  • Which node are you using (preferably, if possible, please attach workflow JSON)?
  • Which n8n version are you using?
  • Where do you see _BLANK_VALUE?
3

Hello Minimal_Feature, welcome to n8n Community! I’ll try to help you.

This is almost certainly not data loss. *_*n8n_BLANK_VALUE is the mask n8n shows for stored secrets. After you click Save, the UI replaces the real value with that placeholder on purpose. The secret is kept, you only need to re-enter it if you want to change it.

Maybe you can try this sanity check:

  • Create a Header Auth credential, where is Header name: Authorization, and the value is Bearer YOUR_TOKEN.
  • Make a test request with HTTP Request:
  • Execute that, and supposedly the output you see like this:
{ "headers": { "Authorization": "Bearer YOUR_TOKEN", ... } }

if you see it, the credential is saved and working.

Maybe thats all you can try it, i hope this will be works. :blush::raising_hands: