Is Zapier down?

Status: Identified We’re aware of an issue affecting the Close CRM integration where some customers may see errors when connecting or reconnecting their Close account in Zapier (for example, “invalid_client”). We’ve identified the failure point and are working with the relevant parties to restore normal authentication as quickly as possible. We’ll share another update as we learn more. If you’re impacted, please retry later. If the issue is urgent, contact Zapier Support at: https://zapier.com/app/get-help with a screenshot of the error.

Status: Resolved This issue affecting the Close CRM integration has been resolved. Customers should now be able to connect or reconnect their Close account in Zapier normally. We have also replayed impacted delayed/held Zap runs that were paused during the incident. If you’re still seeing errors connecting or reconnecting Close, please retry and contact Zapier Support at: https://zapier.com/app/get-help.

Status: Monitoring We have confirmed that the Quota Exceeded errors from Google Drive also affected a small subset of Zap workflows using Google Sheets, Google Docs, Google Slides and Gmail actions. The Google Drive quota exceeded errors have been resolved (https://status.zapier.com/incidents/01KY534ZVKCPV90WN0B6BAY0WY). The majority of affected Google apps Zap runs have been replayed. We are currently monitoring error rates and confirming that all affected Zap runs have succeeded at this point. If you have any questions, please reach out to our Support team at zapier.com/get-help.

Status: Resolved We previously reported quota-exceeded errors affecting a subset of Zap workflows using Google Drive, Google Sheets, Google Docs, Google Slides, and Gmail actions. The underlying issue has been fixed. Affected Zap runs have been replayed, and workflows that were paused due to elevated errors have been restored. No further action is needed on your end. If a Zap run still shows as failed, you can replay it from your Zap history, or contact Support at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help.

Status: Identified Our Engineering has identified an issue with the Google Drive integration hitting intermittent 403 - Quota Exhausted errors across all actions. The team is working on implementing a fix. If you have any questions, please reach out to our Support team at zapier.com/get-help.

Status: Monitoring Our Engineering implemented a fix by rolling back an update that caused the elevated errors. All Zap workflows using Google Drive actions will continue to execute correctly.  Errored runs will be replayed automatically. We continue to monitor performance to confirm all error rates have returned back to baseline. If you have any questions, please reach out to our Support team at zapier.com/get-help.

Status: Resolved The rollback was successful, and the Google Drive quota errors have been resolved. All Google Drive actions are back to normal. Errored runs have been replayed automatically. Many thanks for your patience while we worked through this. If you have any questions, please reach out to our Support team at zapier.com/get-help: http://zapier.com/get-help.

Status: Investigating We've received reports of customers being unable to create new BambooHR connections, or test existing BambooHR connections, within the Zap Editor. Attempts at either result in an error code with response status code 403. We are working with BambooHR to identify the cause of the error and resolve this as quickly as possible. Affected components Zap Editor (Degraded performance)

Status: Monitoring We've identified the cause the issue preventing users from creating new BambooHR connections or testing/updating existing BambooHR connections. We've released an update the we believe will address this issue, and will continue to monitor to confirm the issue is resolved. Affected components Zap Editor (Degraded performance)

Status: Resolved We've resolved an issue that could cause new BambooHR connections or reconnection attempts to fail with an unclear authentication error and status code 403. The issue stemmed from one of the endpoints we used to verify BambooHR connections becoming unreliable. We've updated our connection check to use a more reliable endpoint and corrected the error messaging so any future authentication issues will show a clear, actionable reason. What you need to do: • If your BambooHR Zaps have continued running normally throughout, no action is required. • If you were previously unable to create a new BambooHR connection or reconnect an existing one "reconnect an existing one": https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK29AAFDNP7AS4PQ1NNM6, please try again, this should now succeed. • If you're unsure whether your connection was affected, we recommend testing "testing": https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK296C9MCSX29305AKVZY your BambooHR connection "BambooHR connection": https://zapier.com/app/assets/connections?app=BambooHRCLIAPI from your account settings to confirm. We apologize for any disruption this caused and thank you for your patience. Affected components Zap Editor (Operational)

Status: Investigating We are currently investigating elevated error rates affecting the Translate by Zapier integration. Starting at approximately 2:00pm UTC on July 20, 2026, users of this integration have been experiencing 403 "User Rate Limit Exceeded" errors when attempting to use the translation features. What's Happening Our investigation has identified that the Google Cloud Translation API v2 is returning rate limit errors for requests from the Translate by Zapier integration. This is causing approximately 88% of translation requests to fail. We have confirmed that this issue originates from Google's API, not from Zapier's systems. Who's Affected Affected users may see failed translation steps in their Zaps, though the errors are not automatically disabling workflows. What We're Doing Our engineering team is actively investigating mitigation options. We will provide updates as we make progress. Next Update We expect to have more information soon. We appreciate your patience as we work to resolve this issue.

Status: Resolved Earlier today, some Translate by Zapier requests failed with 403 “User Rate Limit Exceeded” errors due to a Google Integrations Production Google Cloud billing configuration issue. This has been resolved and we’re seeing successful translations again with no ongoing errors. If you had Zap runs fail during the incident window, you may need to replay those runs to complete processing. If you experience any ongoing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience.