N8n credential picker no longer shows shared/personal credentials after update (admin user)

Questions
,
1

Describe the problem/error/question

Github Issue here.

After a recent n8n update, the credential picker in the node editor no longer shows credentials that are shared with me (i.e., credentials not owned by my personal scope), even though I’m an admin and the credential is explicitly shared with my user.

Additionally, existing nodes that were previously configured with those shared credentials still execute successfully, but the UI now displays “No credential” for those nodes. This suggests the workflow/runtime can still resolve the credential, but the editor UI can’t display or re-select it, and I can’t pick the shared credential for new nodes.

Impact: I cannot configure new nodes (or reliably edit existing ones) that require shared credentials, because the credential dropdown does not include the shared credentials.

image
image644×415 13.4 KB

What is the error message (if any)?

“No credential”

Information on your n8n setup

  • n8n version: 2.23.2
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n Cloud
  • Operating system: Linux
2

Hi @eduardochaves

This sounds like a regression issue. Please reach out to help@n8n.io

3

This is a known bug that was introduced in n8n’s frontend UI, The Backend is Fine: The workflow execution engine (runtime) still has full permission to look up and decrypt the shared credentials using the database entry. This is why your existing workflows continue to execute flawlessly in the background.
Workarounds: If you need a new node that uses that specific shared credential, copy a node from an older, working workflow that already utilizes that credential, paste it into your new workflow, and then simply change the action/endpoint configuration while leaving the credential field untouched.

I hope that helps

4

Welcome @eduardochaves

What you’re seeing really looks like a UI regression: the backend still uses your shared credentials, but the credential picker stopped showing them after the update.

Two quick checks that match your situation:

  • Existing workflows that already use those shared credentials still run fine (so the credential is valid and shared correctly).

  • In the editor, the node shows “No credential” and the dropdown no longer lists your shared/personal credentials, so you can’t select them for new nodes.

A few practical things you can try right now:

  • Create a brand‑new node of the same type and see if your shared credential appears in its dropdown; if it does, recreate the affected node instead of editing the old one.

  • Copy a node from an existing workflow that still uses the correct shared credential and paste it where you need it, then just change the action/endpoint without touching the credential field (this keeps the hidden link to the credential while the picker is broken).

  • Double‑check in Settings → Credentials that the credential is still shared with your user / project, and toggle the sharing off/on once to force a refresh.

Since you’re on n8n Cloud and this started right after updating to 2.23.2, I’d also open a support ticket (help@n8n.io) with a short description, screenshots of the picker and the credential settings, and a link to the GitHub issue you already created so the team can confirm and patch this regression.

5

Hey guys thanks for the feedback, but I tested copying and pasting but doesn’t work because on front-end the Node JSON doesn’t have any credential setup. I also tried removing the share and doing again and nothing.

Btw I’m admin, and the only credentials I can use are my personal ones. And some colleages are having same issue under our account.

I didn’t know about this support email, I’ll send n8n a ticket, thanks.

6

A workaround, maybe it works :crossed_fingers:
If you are using an n8n Cloud plan that supports multiple users and role permissions (Advanced or Enterprise), the best way to bypass the broken user-to-user sharing dropdown is to leverage Project Environments:

Have an Instance Admin create a new shared Project workspace.
Move the primary credentials from your personal workspace into this new Project workspace.
Move the workflows that need these keys into the exact same Project space.
Add your colleagues as members of this Project.
Let me know if this works

7

Unfortunatelly I can’t because we’re already within the 3 projects plan limit and we cannot share these credentials with those teams.