n8n - ✅(Solved) Fix Credential Menu not pulling saved credentials [1 pull requests, 1 comments, 2 participants]

n8n2026-04-09 18:43:49

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

n8n-io/n8n#28272•Fetched 2026-04-10 03:44:28

View on GitHub

Comments

Participants

Timeline

Reactions

Author

looptrail

Participants

looptrail

n8n-assistant[bot]

Timeline (top)

labeled ×3commented ×1mentioned ×1subscribed ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

error: all

PR fix notes

PR #28361: fix(editor): Show saved credentials for HTTP Request dynamic auth types

Repository: n8n-io/n8n
Author: muhammadosama984
State: open | merged: False
Link: https://github.com/n8n-io/n8n/pull/28361

Description (problem / solution / changelog)

Summary

The HTTP Request node stores the active auth mode in parameters (predefinedCredentialType + nodeCredentialType, or genericCredentialType + genericAuthType), not only in the node type’s static credentials list (which is effectively SSL-only for HTTP Request).

The credential picker could show no saved credentials (or target the wrong credential slot) because:

getCredentialTypesNodeDescriptions: When the selected credential type was not yet present in the credential-types store, the code fell back to the node’s static credentials array. For HTTP Request that did not reflect the active nodeCredentialType, so the UI could not list the right saved credentials.
getNodeTypeDisplayableCredentials: It only surfaced credentials from the node description. Dynamic HTTP Request auth types from parameters were omitted, which broke downstream helpers (for example setup flows that derive required credential types from displayable credentials).

This PR fixes both paths for HTTP Request and HTTP Request–like node types, and adds unit tests for the store helper and getNodeTypeDisplayableCredentials.

How to test

Add an HTTP Request node, set Authentication to Predefined Credential Type, pick a service credential type (for example Anthropic), and open the credential selector: your saved credentials for that type should appear and remain selectable after saving and reloading the workflow.
Smoke-test Generic Credential Type and SSL certificates on HTTP Request to confirm no regression.

Related Linear tickets, Github issues, and Community forum posts

Fixes https://github.com/n8n-io/n8n/issues/28272

Review / Merge checklist

I have seen this code, I have run this code, and I take responsibility for this code.
PR title and summary are descriptive. (conventions)
Docs updated or follow-up ticket created.
Tests included.
PR Labeled with Backport to Beta, Backport to Stable, or Backport to v1 (if the PR is an urgent fix that needs to be backported)

Changed files

packages/frontend/editor-ui/src/app/utils/nodes/getNodeTypeDisplayableCredentials.test.ts (added, +146/-0)
packages/frontend/editor-ui/src/app/utils/nodes/nodeTransforms.ts (modified, +47/-2)
packages/frontend/editor-ui/src/features/credentials/__tests__/credentials.store.test.ts (modified, +45/-0)
packages/frontend/editor-ui/src/features/credentials/credentials.store.ts (modified, +10/-1)

RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

The node in n8n is not remembering the saved credentials, likely due to a mismatch between the credentials saved in the UI and those referenced in the node's JSON configuration.

Guidance

Verify that the credentials section in the node's JSON configuration matches the credentials saved in the UI. Specifically, check that the httpHeaderAuth id and name correspond to the intended Anthropic API credentials.
Update the credentials section in the node's JSON configuration to reference the correct Anthropic API credentials.
Check for any other nodes or workflows that may be using the same credentials and ensure they are also updated correctly.
After updating the credentials, try reloading the workflow and verify that the node is using the correct credentials.

Example

No code snippet is provided as the issue seems to be related to configuration rather than code.

Notes

The issue may be specific to the n8n version (2.15.0) or the docker environment. It's also possible that there's a caching issue or a bug in the n8n UI that's causing the credentials to not be saved correctly.

Recommendation

Apply a workaround by manually updating the credentials section in the node's JSON configuration to reference the correct Anthropic API credentials. This should resolve the issue until a more permanent fix can be found.

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?

#api #model compatibility #GPU setup #container setup #orchestration issue

Still need to ship something?

×6

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

Data

Security

Network

Code

UI/UX

Text

System

Multimedia

Protocol

API

Engineering

n8n - ✅(Solved) Fix Credential Menu not pulling saved credentials [1 pull requests, 1 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Describe the problem/error/question

What is the error message (if any)?

PR fix notes

PR #28361: fix(editor): Show saved credentials for HTTP Request dynamic auth types

Description (problem / solution / changelog)

Summary

How to test

Related Linear tickets, Github issues, and Community forum posts

Review / Merge checklist

Changed files

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow/screenshots/recording

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

TRENDING

n8n - ✅(Solved) Fix Credential Menu not pulling saved credentials [1 pull requests, 1 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Describe the problem/error/question

What is the error message (if any)?

PR fix notes

PR #28361: fix(editor): Show saved credentials for HTTP Request dynamic auth types

Description (problem / solution / changelog)

Summary

How to test

Related Linear tickets, Github issues, and Community forum posts

Review / Merge checklist

Changed files

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow/screenshots/recording

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

RELATED_DISCOVERY

TRENDING