Credential Menu not pulling saved credentials

[jordanwilliamsLT]

Describe the problem/error/question

I am using Claude Code to build flows in n8n. The behavior/bug I am experiencing is after Claude code builds a new workflow, I manually reload the workflow in Chrome and then go in and make sure that the authentication credentials are correct for each node that is calling an API. The bug is that when I do that, the node in n8n seems to refuse to remember or connect to the credentials that I've saved within my account and asks me to enter new credentials. Upon testing, I've discovered that when I enter new credentials, they are saved correctly, but, as you might guess, I end up with multiple credentials for the same API.

What is the error message (if any)?

None

Please share your workflow/screenshots/recording

Here's the JSON of that node and it's clearly trying to pull a different saved Auth (a customer Header Auth I saved for Prompt Layer). But when a) that is not what is reflected in the UI (see screenshot) and b) when I try to update it in the UI, my saved Anthropic credentials don't show as available.

{
"nodes": [
{
"parameters": {
"method": "POST",
"url": "https://api.anthropic.com/v1/messages",
"authentication": "predefinedCredentialType",
"nodeCredentialType": "anthropicApi",
"sendHeaders": true,
"headerParameters": {
"parameters": [
{
"name": "anthropic-version",
"value": "2023-06-01"
}
]
},
"sendBody": true,
"specifyBody": "json",
"jsonBody": "=$json.claudeBody",
"options": {}
},
"id": "83527983-16db-47c3-ae84-57675b626fc3",
"name": "Generate Claude Overview",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
1200,
304
],
"credentials": {
"httpHeaderAuth": {
"id": "xxxxxxxxxxxxxxxxxxx",
"name": "PromptLayer Connector"
}
}
}
],
"connections": {
"Generate Claude Overview": {
"main": [
[]
]
}
},
"pinData": {},
"meta": {
"aiBuilderAssisted": true,
"instanceId": "xxxxxxxxxxxxxxxxxxx"
}
}

<img width="751" height="482" alt="Image" src="https://github.com/user-attachments/assets/70e34f88-7722-43cf-aaaf-31515f8ec9aa" />
<img width="1223" height="919" alt="Image" src="https://github.com/user-attachments/assets/a7ae6952-3ecc-4a87-811a-18a584151b88" />

## Share the output returned by the last node
<!-- If you need help with data transformations, please also share your expected output. -->


## Debug info

### core

- n8nVersion: 2.15.0
- platform: docker (cloud)
- nodeJsVersion: 24.13.1
- nodeEnv: production
- database: sqlite
- executionMode: regular
- concurrency: 5
- license: enterprise (sandbox)

### storage

- success: all
- error: all
- progress: false
- manual: true
- binaryMode: filesystem

### pruning

- enabled: true
- maxAge: 168 hours
- maxCount: 2500 executions

### client

- userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36
- isTouchDevice: false

Generated at: 2026-04-09T18:35:03.537Z

[n8n-assistant]

Hey @looptrail,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-7669".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-7669

[devnucleus950]

Hey, I’d like to work on this issue.

From what I understand, this seems to be caused by a mismatch between the nodeCredentialType (anthropicApi) and the assigned credential type (httpHeaderAuth), which leads to the UI not showing the correct saved credentials.

Is that the correct direction to investigate? Also, please let me know if someone is already working on this.

[jordanwilliamsLT]

Hi - thanks for the reply. Importantly, I was seeing this behavior across all my credentials not just Anthropic. The behavior was I would select an author type for which I had saved credentials and none would show. The resolve appears to have been restarting Chrome and some passage of time (caching?) Jordan

…

On Fri, Apr 10, 2026 at 8:10 PM Aditya ***@***.***> wrote: *adityainit* left a comment (n8n-io/n8n#28272) <#28272 (comment)> Hey, I’d like to work on this issue. From what I understand, this seems to be caused by a mismatch between the nodeCredentialType (anthropicApi) and the assigned credential type ( httpHeaderAuth), which leads to the UI not showing the correct saved credentials. Is that the correct direction to investigate? Also, please let me know if someone is already working on this. — Reply to this email directly, view it on GitHub <#28272 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CAB3JRXX3RA5MWOGRTY5VCD4VGZSHAVCNFSM6AAAAACXS5CSQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMRYGAZDOOBVG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[devnucleus950]

Thanks for the clarification!

Since it seems like this might be related to caching or a transient issue, I’ll try to reproduce it on my end. If I’m unable to consistently reproduce the bug, I’ll look for another issue to contribute to.

Appreciate the update!

Aditya

[cafesao]

This makes me uneasy about using n8n. I updated our company's n8n instance to the version tagged as stable, but when running the workflows I started getting credential errors, and searching for the issue led me here.

How can a version be tagged as stable without having an EFFICIENT testing pipeline to ensure that already implemented features work as expected??? We've now adopted a rule to wait 2+ weeks after a new stable release to avoid situations like this.

Anyway, thanks for the PR 👍🏻 — I hope it fixes this problem so I can safely update to the "stable" version.

[n8n-assistant]

Fix got released with n8n@2.19.0