Encountering "Precondition check failed" Error in Gmail Node After Recent Update

[ferreret]

Describe the problem/error/question

After updating my n8n instance to the latest version, I’ve started encountering issues with the Gmail node. Prior to the update, my workflows involving this node functioned without any issues. This error arises during operations such as sending emails messages.

Error message

{
  "error": {
    "code": 400,
    "message": "Precondition check failed.",
    "errors": [
      {
        "message": "Precondition check failed.",
        "domain": "global",
        "reason": "failedPrecondition"
      }
    ],
    "status": "FAILED_PRECONDITION"
  }
}

n8n setup

• n8n version: 1.79.3
• Database (default: SQLite): SQLite
• n8n EXECUTIONS_PROCESS setting default
• Running n8n via Docker
• Operating system: Ubuntu 24.04

Steps Taken So Far:

1. Verified Credentials: I have re-authenticated my Google credentials within n8n to ensure they’re valid.
2. Checked API Access: Confirmed that the Gmail API is enabled in the Google Cloud Console.
3. Reviewed Permissions: Ensured that the necessary scopes are authorized for the application.
4. Tested Other Nodes: Other Google-related nodes (e.g., Google Sheets) are functioning correctly, suggesting the issue is isolated to the Gmail node

[n8n]

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:

[Exnav29]

Hey @ferreret, this is going to sound basic, but it has worked for me in the past. Can you delete the Gmail node and re-add it?

[ferreret]

Thanks for the answer,

yes, I’ve tried but still doesn’t work

[markup]

I have the same problem after upgrading to n8n:1.80.5 and also after downgrading to n8n:1.78.0.

• n8n version: 1.80.5
• Database: postgres
• n8n EXECUTIONS_PROCESS setting: default
• Running n8n via: Docker
• Operating system: Windows 10 Pro

[markup]

Update:
I found out that it works when you use a google account with an @gmail.com address. I did my first tests with another google account which is associated with an email address from a different domain, that’s where the node failed to execute successfully.

[Yo_its_prakash]

• Ask your Workspace admin to enable “Less secure app access” for your account

This issue specifically affects non-Gmail domains due to stricter security policies on Google Workspace accounts compared to regular Gmail accounts.

If my solution helped solve your issue, please consider marking it as the answer! A like would make my day if you found it useful!

[ferreret]

Thank you, this was really the problem.