Google Service Account Credentials

Questions
, ,
1

Hi everyone,

I am using the latest version of N8N Self-Hosted Community Edition and am receiving 401 errors when trying to use Google Service Account credentials.

What is the current method of authenticating with a Service Account, or is there a more preferred method? I know OAuth 2.0 is an option, but I don’t want to authenticate with my Google Account for a production N8N system.

I am looking at using API Keys and Query Auth, also. The Service Account method seems to connect successfully but I can never invoke my Cloud Run hosted API endpoint without 401 issues.

Greatly appreciate any insights or recommendations!

Thanks!

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

Welcome to the community @the-chronomancer !

Tip for sharing information

Pasting your n8n workflow

Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.

```
<your workflow>
```

That implies to any JSON output you would like to share with us.

Make sure that you have removed any sensitive information from your workflow and include dummy or pinned data with it!

Using Google Service Account is OK, works for me. Did you follow the guide Google Service Account | n8n Docs? Make sure not to miss any steps.

4

Yes, I did. I get a 401 every time I use the Service Account credentials trying to invoke a Cloud Run function I have which houses an API, regardless of the scope I use.

I ended up using an API Key with Header Auth for now

Should the Service Account integration allow the HTTP Request node to invoke a Cloud Run function?