n8n - 💡(How to fix) Fix Issues with my shared / personal credentials (where are they ? ) [5 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

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…
GitHub stats
n8n-io/n8n#28230Fetched 2026-04-10 03:44:39
View on GitHub
Comments
5
Participants
4
Timeline
17
Reactions
0
Timeline (top)
commented ×5labeled ×3subscribed ×3mentioned ×2

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

I'm building workflows that call the GitHub API.

I created shared credentials so they can be used by everyone. However, when I open the credentials list, they don't appear. If I create a new empty credential just to add an item to the list, then suddenly all the existing credentials appear. At that point, I can select the correct credential.

But when I run the workflow, it reports that no credential is set. When I edit the workflow again, the credential has disappeared.

I've already restarted the platform and cleared my browser cache, but the issue persists.

At this point, I'm blocked and unable to proceed.

What is the error message (if any)?

Problem in node ‘xxxxxx‘ Node "xxxxx" does not have access to the credential

Please share your workflow/screenshots/recording

Step 1 <img width="752" height="328" alt="Image" src="https://github.com/user-attachments/assets/ca94343e-79ca-473c-abaf-54f2af598ced" /> Step 2 <img width="1001" height="616" alt="Image" src="https://github.com/user-attachments/assets/43d2c0d8-8f0f-46ec-bd76-989efaebf853" /> Step 3 - we can see all of them <img width="721" height="247" alt="Image" src="https://github.com/user-attachments/assets/ddc1b491-3716-4462-a7fb-b636da958085" /> Step 4 - I select the good one <img width="713" height="320" alt="Image" src="https://github.com/user-attachments/assets/deee54d5-bb39-421d-87f6-8d8d4bb2c800" /> Step 5 - workflow failed... <img width="572" height="160" alt="Image" src="https://github.com/user-attachments/assets/ab3417b3-7e39-47d1-92a6-7b14fddd0a1d" />

My credential is good...

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-09T07:12:14.868Z

extent analysis

TL;DR

The issue can be resolved by re-checking the credential configuration and ensuring it is properly set for the workflow node.

Guidance

  • Verify that the credential is correctly configured and assigned to the workflow node, as the error message "Node 'xxxxx' does not have access to the credential" suggests a permission or configuration issue.
  • Check the workflow settings to ensure that the credential is properly selected and applied to the node, as the issue seems to be related to the credential not being persisted or recognized by the workflow.
  • Review the screenshots provided to ensure that the credential is correctly selected in the workflow editor, as the images show the credential being selected but not being persisted.
  • Investigate potential issues with the n8n version (2.15.0) or the docker environment, as these may be contributing to the problem.

Example

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

Notes

The issue may be related to a bug or limitation in the n8n version being used, and upgrading to a newer version may resolve the issue. However, without further information, it is difficult to determine the root cause.

Recommendation

Apply workaround: Re-check and re-configure the credential settings for the workflow node, as this seems to be the most likely cause of the issue.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING