Gmail Trigger shows error: Credential does not exist for type gmailOAuth2

Questions
1

Hi, I’m using n8n Cloud and having issues with Gmail credentials.

Problem:

  • I create a Gmail OAuth2 credential
  • It shows “Account Connected”
  • After saving, the Gmail Trigger shows: “Credential with ID does not exist for type gmailOAuth2”
  • The Save button is also blocked sometimes after connecting

Steps I tried:

  • Deleted and recreated credentials multiple times
  • Enabled Gmail API in Google Cloud Console
  • Added test users in OAuth consent screen
  • Tried in incognito mode

n8n Cloud version, Gmail Trigger node.

Any help appreciated!Describe the problem/error/question

4

Hi @Joaquin_lema Welcome! taht “Credential with ID does not exist” error on cloud usually means the node is still pointing to the old deleted credential ID, after you recreate the cred you have to reopen the Gmail Trigger node, click the credential dropdown and re-select the new one, then save the workflow before running. here’s a clean trigger to import and re-link:

{ "nodes": [ { "parameters": {"pollTimes": {"item": [{"mode": "everyMinute"}]}, "simple": true, "filters": {}}, "name": "Gmail Trigger", "type": "n8n-nodes-base.gmailTrigger", "typeVersion": 1, "position": [400, 300] } ], "connections": {} }

drop your fresh gmailOAuth2 cred onto the node, save the workflow, then activate

6

welcome to the n8n community @Joaquin_lema
I’d capture the browser console output when saving the credential or the trigger, then share it with n8n support together with the workflow ID and credential type, because that points to a UI or credential-reference persistence issue rather than a Gmail API permission problem.
This looks like the Gmail Trigger is not persisting the credential reference correctly