When attempting to connect to the Google Maps API, I am able to successfully create credentials. However, when I run, the node returns a “credentials not found” error. I am not the owner of the n8n instance, but my account has admin privileges. Using the exact same credentials on a personal instance, the node works as expected, I can connect and retrieve data successfully. This suggests that, despite having admin privileges, my account does not have the necessary access to credentials on this instance, though it should.
What is the error message (if any)?
Problem in node ‘HTTP Request’ –> Credentials not found
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Share the output returned by the last node
Information on your n8n setup
core
n8nVersion: 1.120.3
platform: docker (cloud)
nodeJsVersion: 22.21.0
nodeEnv: production
database: sqlite
executionMode: regular
concurrency: 20
license: community
storage
success: all
error: all
progress: false
manual: true
binaryMode: filesystem
pruning
enabled: true
maxAge: 720 hours
maxCount: 25000 executions
client
userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/142.0.0.0 safari/537.36
I had this same problem recently and the short version is: the credential is valid, but your n8n account isn’t allowed to use it on that instance.
On the Community edition of n8n, credentials are always private to the user who created them. They are not automatically shared with other admins or users. So even though you have admin rights, you still can’t use a credential that belongs to someone else. That is why your personal instance works fine, but the shared one gives “credentials not found”.
What most likely happened here is that the workflow you are trying to run was created by a different user, and the HTTP Request node is still referencing a credential created by that user. When you click execute, n8n checks permissions and can’t find access to that credential under your account.
What you can do now:
Create a new workflow under your own account and add the Google Maps credential directly from the HTTP Request node. Then run it.
or
Ask the instance owner to open the workflow, select a credential they created, and save it again.
If multiple people need to share the same credentials on that installation, n8n requires a paid plan that includes proper credential sharing.
So the fix is simply to make sure the workflow and the credential are both owned by the same user, let me know if the issue still persists after these fixes.
Thank you Anshul for the quick reply. I did not inherit the workflow. I have tried it in every possible way including creating my own workflow and creating credential from within the node, and creating the credentials separarty and picking it up. No matter what I do it doesn’t work (both the workflow and credentials are mine), not shared. That said, it works fine for the other user who happens to be “owner”.
Moreover, our instance is a paid version if it helps.
