Google Drive credentials

Questions
,
1

Describe the problem/error/question

“On my gear.app.n8n.cloud instance, all nodes with credentials fail with ‘Node does not have any credentials set’ even though the credentials are configured, in Global sharing, and visually selected. The problem occurs with Google Drive, Google Docs, HTTP Request with Bearer Auth, and Code nodes. I’ve recreated the nodes from scratch and the problem persists.”

What is the error message (if any)?

Please share your workflow

DOCS y SHEETS

Share the output returned by the last node

Node does not have any credentials set

Information on your n8n setup

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

Hi @Gerardo_Emmanuel_Agu

Try creating a new credential that is not shared globally (private to the owner) and assign it to a node to see if the “Global sharing” mechanism is the specific point of failure. If a private credential works, the issue is isolated to the sharing permission logic.

Because this is happening on a managed .n8n.cloud instance and affects multiple node types (Google, HTTP Request, Code), it likely requires a fix at the infrastructure or database level that only the n8n cloud team can apply. I recommend opening a support ticket and referencing the specific error and the fact that it persists across recreated nodes and global sharing settings.

3

I will open a ticket since I already tried with a personal sharing credential.

Thanks for the tip

4

Hey there! This is a very frustrating situation. Getting a “Node does not have any credentials set” error when they are visibly selected is a classic sign of an underlying issue with how n8n is saving or applying those credential references, especially on Cloud instances like gear.app.n8n.cloud.

Since you’re on n8n Cloud, direct server debugging isn’t possible, but here are the immediate troubleshooting steps to force a backend sync:

1. Force Re-save/Re-select Explicitly
Sometimes the underlying ID linking the node to the credential gets corrupted in the workflow JSON.

  • Go to each problematic node.
  • Open the Credentials dropdown and select None.
  • Click Save on the workflow.
  • Re-open the node, re-select the correct credential, and Save again.
  • Execute the node to test. This forces n8n to re-write the credential reference.

2. Verify & Test Connections

  • Go to the Credentials sidebar.
  • Click on the failing credentials (Google Drive, HTTP, etc.) and click Test Connection (if available). Ensure they all actually succeed from the backend perspective.

3. The “New Credential” Isolation Test

  • Create a brand new HTTP Basic Auth credential with dummy values (username: test, password: test).
  • Create a new, simple workflow with just an HTTP Request node pointing to https://httpbin.org/basic-auth/test/test.
  • If this also fails, the problem is a systemic backend desync on your specific instance. If it works, the issue is specific to your older credential IDs.

Next Steps:
If none of these force a sync, this points to a caching or database desync on the managed cloud side. You’ll need to contact n8n support directly with your instance ID (gear.app.n8n.cloud) and mention you’ve already tried forcing a credential ID refresh.

P.S. I actually ran your exact forum post through n8n Mastery / Sensei (a free, gamified AI Co-pilot I just built for the n8n community), and it provided this exact step-by-step troubleshooting guide specifically tailored for Cloud instances!

I’m attaching a screenshot of its full analysis below. If you want to debug workflows and errors instantly right next to your n8n canvas, you can check it out here: https://n8n-sensei-app-nu.vercel.app/

Good luck, hope it syncs up for you soon!

image
image1920×1080 212 KB