Gmail API 403 error

About 24 hours ago I enabled the Gmail API on Google Cloud. I’ve also successfully connected using Gmail 0auth API. During the “Test Step” action I recieve the 403 Error output below.

I’ve also successfully connected Google Sheets / Drive which are working as expected.
I need to be able to send an email after a trigger happens.

Looking through the other community questions it seems other people have had similarisuse with the Gmail API. None of the suggestions helped me though.

Node Type: n8n-nodes-base.gmail
Node version:2.1 (Latest)
n8n version:1.52.2 (Cloud)
using web app url -  https://ourcompany.n8n.cloud/
Google Account that is Google Cloud authorized through n8n is [email protected] 

#Error 403 From google

Forbidden - perhaps check your credentials? (item 0) [item 0]
Gmail API has not been used in project ##### before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/gmail.googleapis.com/overview?project= #####  then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.

Thanks

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:

Hi @quickee

Thanks for posting here and welcome to the community! :partying_face:

Have you enabled the Gmail API in your Google Cloud Console?
https://console.cloud.google.com/apis/library/gmail.googleapis.com

hi thanks for the response!!

Per my initial post - About 24 hours ago I enabled the Gmail API on Google Cloud.

Hey @quickee,

The error you are seeing is coming back from Google and they don’t seem to think the option is enabled.

I would follow the link in the error message and double check for any extra prompts that Google are after. It can sometimes take a bit of time but I would expect it to be working now but following the link they are providing will likely show what the problem is.

thank you, disabling and re-enabling the API fixed the issue. I let it sit for an hour or so before enabling again

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.