I’m running the latest version of n8n cloud.
I’m trying to make it work with Google Cloud Services account for Business. The creds get stuck at testing. Nothing happens. Doesn’t work. I’ve tried everything. Can somebody pls help? Btw, I’m not very technical, just starting out, but have made a few workflows.
Will be very helpful.
So I created a Services credential on Google Cloud for Google Sheets usage. Got the private key, service email ID. Entered that on n8n. Stuck on testing. Doesn’t move.
Hi @aakshey, I am super sorry for this. I actually ran into this myself and have already flagged this to our engineering team.
I’ll keep an eye on the progress and make sure we keep you updated on a fix.
Pls update me as soon as there is an update mate, thank you so much for trying to fix this @MutedJam
Sure thing. Just out of curiosity, are you trying to use a specific node with the service account credentials are you okay with using an HTTP Request node? For the latter you might be able to build a workaround at least (basically handling the authentication as part of the workflow logic rather than through built-in credentials). Happy to set up a quick example for that if it would help
@MutedJam I’m trying to use Google Workspace services like Google Sheets, Gmail, etc. Is it possible to manage this hiccup free while using using the HTTP node with authentication? Can you teach me how? Thank you so much
+1, running on the hosted version, Google Credentials are stuck on the testing, clicking away replaces the key
Just checked in on the current status, a fix is on the way!
@aakshey I can whip up an example showing the basic authentication and how to make a simple authenticated request. However, I will not be able to rebuild all existing Google nodes using pure HTTP requests and code I am afraid 
So I think your best bet here is to wait for the above to be reviewed and published, this should hopefully happen soon!
@MutedJam would love the example showing the basic auth… also running into this service account api credential stuck in “Testing” limbo …
Here you go @Jacob_Boneta:
This workflow will go through the full auth flow (without using n8n credentials), and then make an authenticated request in the last HTTP Request node. This is where you can plug in your own request:
That said, the fix linked above has been merged in the meantime, so the built-in auth should hopefully work again with the next release 
I’m having a similar issue but with Google OAuth. Is this a know issue? I’m on 1.99.1
New version [email protected] got released which includes the GitHub PR 16734.
Hi Jan! I wanna ask about n8n:)
Are there any references that I can read for making custom node for Gemini? Since I can’t use Gemini directly through n8n Node (Must be using LLM Chain), so I wanted to make it one, but I don’t know references for that:)
I have the same issue … stuck on testing
I’m sure entering the right email and privste key for the service account
scopes are also fine
…
In Exprssion mode {{"-----abc-----"}} works.
В “Exprssion” режиме работает. {{“-----api-----”}}
