If you are learning n8n, how do you deal with Gmail flagging your account for automations? I created an account just for that and now I got this when asked to verify I am not a bot, even tho I verify with my phone as well:
It looks like this account was created or used with multiple other accounts to violate Google’s policies. The account might have been created by a computer program or bot. This account became unavailable on May 10, 2026. Starting on Apr 5, 2027, this account will be considered for deletion. If you think your account was disabled by mistake, submit an appeal as soon as possible. You can also download your data from some Google services. This gives you a way to keep your data even if your account is not restored.
That’s why I even added authenticator app to that account, sms-verification so now sure. I am going to appeal but how do you handle this on your end without Google disabling your account?
Describe the problem/error/question
What is the error message (if any)?
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Share the output returned by the last node
Information on your n8n setup
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
This can be a common frustration found when learning automation with a Google account.
Here is how you can circumvent the issue:
-Use the OAuth2 credentials in n8n instead of basic auth or app passwords- Google treats OAuth flows more legitimately.
-Use a more legitimate already existing account(Workspace account) and not a throwaway account, Google has algorithms that look for quickly created accounts that suddenly get loads of API usage from them.
-Space out your test runs, rapid triggers on repeat in a short time span can look like a bot, even when done with OAuth.
When making the appeal, be straightforward in that you were testing automation tools for learning purposes. Sometimes appeals work.
Thank you @AnthonyAtXRay I didn’t warm up the email and singed in from lots of random locations. I Didn’t know google would do that. I submitted an appeal but I will not wait for a response. I will try a Workplace account with an existing account I already use.
This happens because Google flagged your new automation account.
It looks like bot activity, so OAuth gets disabled.
Fix:
-
Don’t use a fresh Gmail for n8n
-
Use an older real account or Google Workspace
-
Avoid heavy API/email sending on new accounts
-
Recreate OAuth credentials after fixing consent screen if needed
@NE_automation That’s a really frustrating situation, especially when you set up the account specifically for automation!
David’s points are solid. I’d add a bit more context on what actually works well long-term:
The root issue: Google’s automated systems flag newly created accounts that immediately start OAuth activity at scale as suspicious. The pattern looks identical to credential-stuffing bots from their side.
What I use and recommend:
-
Google Workspace (paid, from ~$6/mo) - This is the gold standard for production automations. Workspace accounts have much higher trust scores, proper admin controls, and you can configure the OAuth consent screen without going through Google’s app verification. The “The OAuth client was disabled” error basically never happens on Workspace accounts.
-
An aged personal Gmail account (3+ years old, actively used) - If budget is a concern, an older account that has real email history works much better than a fresh one.
-
Gmail App Passwords + SMTP - For just sending email, skip OAuth entirely. Enable 2FA on the account, generate an App Password, and use the Gmail node with SMTP/username+password auth. It’s less feature-rich but rock-solid for sending.
For the disabled account specifically: file the appeal through the Google Account Recovery form. It sometimes takes a few days but they do restore accounts that weren’t actually doing anything malicious.