Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

See the screenshot below.

Please note this is what happens when I attempt to make the connection -- it’s not in the account at all and it is not attached to any workflows. 

 

Hi ​@Nary_a_One 

Try this tip for connecting app accounts to Zapier:

 

​@Troy Tessalone, Sadly, no change! Used both an incognito window and a different browser. 

​@Nary_a_One 

The error message you're seeing from Zapier:

Oh, foo.
Zapier could not connect to your account.
('Gmail throttling https://www.googleapis.com/gmail/v1/users/me/profile', 60)

Explanation:
This message means that Zapier attempted to access your Gmail account using the Gmail API, specifically the endpoint:

https://www.googleapis.com/gmail/v1/users/me/profile

...but was rate limited (throttled) by Google. The (60) indicates a HTTP 429 Too Many Requests error or similar rate-limit condition, and likely suggests that Zapier must wait before trying again (usually 60 seconds or longer depending on the quota usage).

Why it happens:

  • Google enforces quotas per user/account or per project/app to prevent abuse.

  • If too many Gmail API requests are made in a short time period (especially for me/profile calls used for account verification), it can temporarily block additional requests.

  • This is common when connecting the same Gmail account repeatedly or when using multiple Zaps that heavily rely on Gmail.

How to fix it:

  1. Wait and retry: The simplest fix is to wait 1–5 minutes, then click "Try again".

  2. Limit frequent reconnections: If you're repeatedly testing connections, try spacing out your attempts.

  3. Avoid rapid API hits: Ensure that Zaps using Gmail are not making excessive API calls all at once.

  4. Check Gmail quota limits: In Google Cloud Console (if using your own app), review quota usage for the Gmail API.

  5. Reconnect Gmail in Zapier after waiting — sometimes re-authenticating with fewer active Gmail Zaps running helps.

 

Thanks for the insight here, but nothing I try is working. 

I even created a new email in our workspace and linked that up to Zapier with no trouble at all. It seems odd that a single account would be singled out. 

 

​@Nary_a_One 

Try opening a ticket with Zapier Support: https://zapier.com/app/get-help

 

Help links for using Gmail in Zaps: https://zapier.com/apps/gmail/integrations#help

Hi ​@Nary_a_One 👋

I can’t see any ticket open with our support team, were you able to get the connection added successfully?

If not, is there anything different about the one that’s erroring compared to the new email account that is working? Had it sent a lot of emails lately perhaps? Just wondering if the account might have hit a sending limit which caused the connection to it to be throttled as well 🤔 In which case, if you retry to connect the account after 24 hours, is it able to be added successfully? 

Keep us posted on your progress, want to make sure this gets sorted!

Terms & ConditionsAccessibility statement