Zapier

1. investigating 2026-10-21 15:21 UTC

   Some customers may see delayed or missing real-time updates in Zapier Tables, including changes made by collaborators and refreshed formula results. Tables remains available, and underlying formula calculations and triggers continue to run. We are investigating a disruption...

2. identified 2026-10-21 15:52 UTC

   We have identified an issue with an upstream service provider that is affecting real-time updates in Zapier Tables. Some customers may continue to see delayed or missing collaborator changes and refreshed formula results. Tables remains available, and underlying formula...

3. identified 2026-10-21 16:04 UTC

   We continue to await recovery from an issue affecting our upstream service provider. Real-time updates in Zapier Tables may still be delayed or missing, including collaborator changes and refreshed formula results. Tables remains available, and underlying formula calculations...

Excerpts are shortened. Read the full incident on Zapier's status page.

1. identified 2026-10-21 14:10 UTC

   Zaps using BambooHR may encounter errors or fail to retrieve data due to a service disruption at BambooHR. We have identified the issue as an outage affecting BambooHR and are monitoring their service for recovery. The full scope of affected Zaps is still being assessed.

2. monitoring 2026-10-21 14:18 UTC

   We are monitoring the BambooHR integration following the service disruption at BambooHR. Zaps using BambooHR may still encounter errors or fail to retrieve data while we assess recovery. We have not yet confirmed that service is fully restored.

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-16 14:10 UTC

   Users with app approvals enabled may encounter an error when publishing Zaps from Guided Templates. Affected users can create a draft Zap, but cannot complete publishing through the Guided Template flow. We are investigating this behavior and assessing its scope.

2. identified 2026-10-16 15:09 UTC

   We have identified an issue in the Guided Template publishing flow that displays an error instead of allowing users to request approval when publishing approval is required. We have prepared a fix and are completing deployment and production validation. In the meantime, affected...

3. resolved 2026-10-16 15:23 UTC

   We have deployed and verified a fix for the Guided Template publishing issue. Users who require publishing approval now see Request to publish within the Guided Template flow and can successfully submit their Zap for approval instead of encountering an error. Existing approval...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 09:40 UTC

   Some customers experienced permission errors that prevented actions on shared Forms, Canvas, and Tables, even when they had access. We have applied a mitigation and confirmed that previously failing actions are succeeding again. We are monitoring to ensure the recovery holds. If...

2. identified 2026-10-14 09:49 UTC

   On October 14, between 08:25 and 09:17 UTC, some customers experienced permission errors that prevented actions on shared Forms, Canvas, and Tables, even when they had access. We have identified the issue and applied a mitigation and confirmed that previously failing actions are...

3. resolved 2026-10-14 10:29 UTC

   The permission errors affecting shared Forms, Canvas, and Tables have been resolved, and recovery of tasks affected by this incident is complete. If you continue to experience permission errors or have questions about an affected task, please [contact our support...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 08:21 UTC

   Customers using the Zoom Team Chat integration are experiencing authentication errors that prevent their app connections from working. We are investigating these failures and have contacted Zoom support and the integration’s maintainers to help resolve the issue.

2. investigating 2026-10-14 09:08 UTC

   Zoom Team Chat connections continue to experience authentication failures, preventing new connections and causing Zaps using existing connections to fail or be held. We have confirmed that other Zoom integrations are unaffected. We have escalated the issue to Zoom support and...

3. investigating 2026-10-14 15:51 UTC

   We're continuing to work closely with the team at Zoom to resolve the authentication failures affecting Zoom Team Chat connections. Service has not yet been restored. We’ll share another update as soon as we have more information.

4. monitoring 2026-10-14 16:40 UTC

   We're seeing recovery for Zoom Team Chat connections. Existing connections are successfully refreshing, and new connections are working again. Most affected connections should recover automatically over the next 20–40 minutes without requiring you to reconnect. A small number...

5. resolved 2026-10-14 22:28 UTC

   The Zoom Team Chat authentication issue has been resolved. Zoom Team Chat connections experienced authentication failures. This prevented new connections and caused Zaps using existing connections to fail or be held. Other Zoom integrations were not affected. Service has been...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-12 08:39 UTC

   We've identified an issue where some requests made through Custom Actions in Zaps or Zapier MCP include duplicated query parameters. Because of this, some customers may see errors even when their inputs are valid. Not every app or request is affected, since many apps handle...

2. monitoring 2026-10-12 10:12 UTC

   A fix has been deployed that stops Custom Actions and Zapier MCP requests from sending duplicated query parameters. Error rates on affected requests dropped to normal immediately after deployment (~09:40 UTC). Not every request failed during the issue, and we have not identified...

3. resolved 2026-10-12 10:27 UTC

   The issue causing duplicated query parameters on some Custom Actions and Zapier MCP requests has been resolved. Starting October 7, a deploy caused some outbound requests to include duplicate query parameters, which a subset of connected apps rejected even when inputs were...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Security incident or emergency response to a vulnerability. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 17:07 UTC

   We are investigating an issue where file links hosted on Zapier’s file storage (`zapier-dev-files.s3.amazonaws.com`) may be blocked or show a security warning because the domain has been flagged in Google Safe Browsing. What’s affected • Opening or downloading files from Zapier...

2. investigating 2026-10-09 19:06 UTC

   Our Security team continues to work to mitigate the issue and has reached out to Google's team for help resolving the "dangerous site" flag when opening files hosted on Zapier storage while Chrome's Safe Browsing is enabled. This issue primarily affects Tables and Forms users,...

3. investigating 2026-10-09 21:20 UTC

   Our team is continuing to investigate the "dangerous site" flag when opening files hosted on Zapier storage while Chrome's Safe Browsing is enabled. We are awaiting confirmation from Google that the issue is remediated. Users of Tables and Forms are the most likely to run into...

4. identified 2026-10-10 03:16 UTC

   We have received information from Google about the "dangerous site" flag on our file storage domain, and our Security team is now removing the files Google identified as dangerous to restore access. Once this cleanup is complete, we will work with Google to have the flag...

5. identified 2026-10-10 03:50 UTC

   We've completed the initial cleanup and are now collaborating with the Google team to determine the next steps needed to clear the "dangerous site" flag on our file storage domain. During this period, your files that passed through Zapier remain safe, and Zaps, Tables, and Forms...

6. resolved 2026-10-12 13:04 UTC

   We have worked with Google, and we can confirm this issue is now resolved. Files passing through Zapier worked normally during this time, and were safe to download. The file links are no longer being incorrectly flagged as a dangerous site. Thank you for your patience while we...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 18:54 UTC

   Our Engineering team is aware of an issue affecting users who sign into [Zapier.com](http://Zapier.com "Zapier.com") using Facebook or Microsoft Single Sign-On (SSO). Users logging into Zapier with these services will see a blank screen after authenticating. The login...

2. monitoring 2026-10-05 19:42 UTC

   Our Engineering team has identified the issue and has released a fix. We're now monitoring our systems to see if there are any other problems that could result from the fix.

3. resolved 2026-10-05 19:46 UTC

   The issue is now considered resolved, with both Facebook and Microsoft single sign-on working as expected. If you find yourself still unable to log in, please reach out to our Support team at [zapier.com/get-help](http://zapier.com/get-help "zapier.com/get-help") Thank you for...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-09-28 12:13 UTC

   Azure DevOps connections are failing because the OAuth client secret has expired. We have identified the issue, and we are currently investigating this further. Only Zaps using the Azure DevOps connection are affected.

2. monitoring 2026-09-28 12:40 UTC

   We have found and resolved the issue affecting the connection. If the connection still shows expired, manually testing the connection should restore it.

3. resolved 2026-09-28 13:18 UTC

   This has been fully resolved. If you still face this issue, please reach out to our support team via the [Get help and support with Zapie](https://help.zapier.com/hc/en-us/articles/8496213764877-Get-help-and-support-with-Zapier "Get help and support with Zapie")r channels

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-21 15:30 UTC

   Our team is currently investigating an issue with Agent runs (from agents.zapier.com) intermittently experiencing 429 errors for some customers. We're working to confirm the root cause and implement a fix as soon as possible. AI by Zapier runs are not affected by this incident....

2. identified 2026-09-21 17:57 UTC

   The team has identified the issue to be an intermittent overload of a service powering: • Agent runs (agents.zapier.com) • AI by Zapier executions As a result, some agent runs and AI by Zapier executions hit 429 errors. We will be working on replaying affected agent runs or Zap...

3. resolved 2026-09-21 19:27 UTC

   The issue intermittently affecting Agent runs and Zap runs using AI by Zapier has been resolved. The confirmed impact window goes from September 18, 2026 at 2:00am UTC to today, September 21, at 15:00 UTC. Our team continues to work with our service provider to prevent this...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-09 17:51 UTC

   We're currently experiencing an issue where the Zap History page is not displaying recent Zap runs happening from today, September 9, 2026 starting at approximately 12:39PM EST. Zap runs are still processing normally, but can't be accessed or reviewed at the moment. We're...

2. identified 2026-09-09 18:14 UTC

   We've identified the root cause for Zap runs not displaying in the Zap History, and our Engineering team is working on a resolution. Zap runs are slowly appearing again in the Zap history, and we'll confirm once all Zap runs can be accessed. For any questions, please reach out...

3. monitoring 2026-09-09 18:59 UTC

   The Engineering team has implemented a fix for this issue, and Zap runs continue to load into the Zap History. Executions have not been affected: Zap runs are executing normally. However, the Zap run data was not rendering in the Zap history correctly. We appreciate your...

4. resolved 2026-09-09 19:41 UTC

   We have implemented a fix regarding Zap history runs not showing, so they should be available in your Zap history page now. If you have questions or need help, please contact our Support team at: [zapier.com/get-help](http://zapier.com/get-help "zapier.com/get-help").

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-09-08 14:06 UTC

   A brief infrastructure issue between approximately 8:15–9:50 AM ET caused some Zap workflows using webhook triggers to not fire, and some Zap action steps to fail. The issue has been resolved, and Zap Runs are processing normally. We're reviewing affected accounts and replaying...

2. resolved 2026-09-08 17:08 UTC

   The issue causing some Zap workflows to not trigger from webhooks or fail on action steps between approximately 8:15–9:50 AM ET has been resolved. If you're still seeing issues with a Zap that should have run during this window, contact Support:...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-01 12:03 UTC

   Customers using Freshservice webhook triggers may not receive new updates in their Zaps. We are investigating the disruption with Freshservice and will share further information as it becomes available.

2. investigating 2026-09-03 14:16 UTC

   We are still investigating the disruption with Freshservice and have touched base with their team to continue digging into this. We will continue to share further information as it becomes available. We appreciate your patience while our team works on this.

3. investigating 2026-09-03 21:39 UTC

   We’re still investigating the disruption with Freshdesk. If you are experiencing issues related to this, please reach out here: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

4. investigating 2026-09-04 19:08 UTC

   The Freshservice disruption is still under investigation. The Freshservice team has confirmed the issue and is working to implement a fix. We’ll provide the next update once we know more. If you’re experiencing this issue, please reach out to our Support team:...

5. resolved 2026-09-07 12:44 UTC

   Freshservice webhook triggers are now delivering to Zapier again following a fix deployed by Freshservice. We’ve confirmed incoming webhook activity has resumed and are continuing to monitor volumes. If you experience ongoing issues, contact Support by clicking above or go to:...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-28 14:35 UTC

   We're currently investigating an issue affecting Tables, Chatbots, and Forms for some users. Affected users may find that existing Tables, Chatbots, or Forms are not loading and are instead being redirected to a creation page. If you need help in the meantime, contact Support:...

2. monitoring 2026-08-28 15:01 UTC

   A fix has been implemented for the issue affecting Tables, Chatbots, and Forms. These should now be loading as expected for affected users. We are continuing to monitor to confirm full stability. We will post a final update within 24 hours. If anything still seems off, contact...

3. resolved 2026-08-28 15:35 UTC

   The issue affecting Tables, Chatbots, and Forms has been resolved as of approximately 15:00 UTC. Some users were unable to load existing Tables, Chatbots, or Forms and were redirected to a creation page instead. All affected surfaces — Tables, Forms, Chatbots, and...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-26 16:55 UTC

   Some customers may experience intermittent delays or failures with instant triggers, which can prevent workflows from starting. We are investigating the issue and working to restore normal processing. We will provide updates as soon as possible.

2. investigating 2026-08-26 17:24 UTC

   We're continuing to investigate a small number of workflows that failed to start between approximately 9:00–9:20 AM UTC on August 25. Affected triggers did not fire during this window. No data has been lost — failed triggers can be replayed once the issue is resolved. Our team...

3. monitoring 2026-08-26 18:59 UTC

   A fix has been implemented and we are monitoring the results. We have not seen any new instant trigger failures since approximately 10:26 AM PDT (17:26 UTC). The change we deployed adds automatic retries for the failure that was preventing a small number of triggers from firing,...

4. resolved 2026-08-26 21:41 UTC

   Instant trigger processing has returned to normal. We have successfully replayed the affected triggers and continue not to see any impacted Zap runs, so the incident is now resolved. If you have any questions, please reach out to our support team:...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-21 23:48 UTC

   We have reports that users who try to create new app connections or reconnect existing ones for ActiveCampaign receive a 403 error. This causes the connection to fail. Our Engineering team is looking into the issue and will follow up as soon as we learn more. If you're unable to...

2. monitoring 2026-08-22 01:45 UTC

   The issue with ActiveCampaign app connections returning a 403 error has been resolved. Authentication and integration are now functioning normally, and Zap runs using ActiveCampaign aren't impacted by this going forward. Our team is currently investigating which Zap runs were...

3. resolved 2026-08-22 02:19 UTC

   The issue with ActiveCampaign app connections and runs returning a 403 error has been fully resolved. Authentication and integration are functioning normally again. Impacted runs during the incident period have been replayed successfully. If you're experiencing any issues,...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-21 09:40 UTC

   We’re investigating an issue affecting Salesforce integrations in Zapier. Some customers may see Salesforce connections disconnect, trigger authentication failures, or Zaps held while we investigate. Zap Runs that use Salesforce triggers may be delayed or fail to fire until...

2. investigating 2026-08-21 10:49 UTC

   We are continuing to investigate an issue affecting Salesforce integrations in Zapier. Some Salesforce connections were invalidated and may show as expired or disconnected in My Apps. How to tell if you’re affected • Go to My Apps:...

3. resolved 2026-08-25 14:20 UTC

   Salesforce connections have recovered and authentication errors have returned toward normal levels. Customers should now be able to use their Salesforce integrations normally. We will continue to monitor recovery.

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-19 16:07 UTC

   We are investigating reports of invalid ID errors related to Pipedrive triggers/actions. If you are running into this issue, please reach out to us at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

2. monitoring 2026-08-19 16:39 UTC

   Errors/issue related to Pipedrive invalid IDs are recovering, and we'll continue to monitor this. If you're still encountering this issue, please reach out to us at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

3. investigating 2026-08-19 16:45 UTC

   We are investigating the affected Zaps regarding the invalid ID errors. If you are experiencing this issue or have any questions, please reach out to us at[ https://zapier.com/app/get-help](https://zapier.com/app/get-help " https://zapier.com/app/get-help")

4. resolved 2026-08-19 19:36 UTC

   Errors related to Pipedrive invalid IDs are resolved. If you have any further questions, please reach out to us: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-18 23:50 UTC

   We're currently experiencing an issue affecting Zapier Functions. Users attempting to create, edit, or run Functions may encounter errors or be unable to access the service. Zaps and other Zapier services continue to operate normally. No data loss is expected. If you are...

2. resolved 2026-08-18 23:58 UTC

   The issue affecting Zapier Functions has been resolved. Functions are now operating normally. During this incident, users were unable to create, edit, or run Functions. No data loss occurred. Zaps and other Zapier services were not affected during this time. If you are still...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-18 17:21 UTC

   We're currently investigating an issue where our [Contact Sales](https://zapier.com/l/contact-sales "Contact Sales") form on the homepage does not load. Our team is actively working on identifying and resolving the issue. In the meantime, if you would like to contact our Sales...

2. identified 2026-08-18 18:06 UTC

   Our Engineering team has observed increased traffic to our Contact Sales form, causing it to reach our vendor's rate limit and fail to load. We're continuing our work to resolve the issue, but if you need to contact our Sales team and are unable to load the form, please feel...

3. monitoring 2026-08-18 20:54 UTC

   We’ve deployed a fix for the issue that caused some [Contact Sales forms](https://zapier.com/l/contact-sales "Contact Sales forms") to fail to load. We’re monitoring the form closely to confirm the improvement holds. If you need to contact our Sales team and are unable to load...

4. resolved 2026-08-19 18:36 UTC

   After monitoring traffic, we're seeing forms respond as expected. We now consider the issue resolved. Thank you for your patience as we worked to resolve the issue.

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-17 20:49 UTC

   We are currently investigating an issue where our Contact Sales form is not rendering correctly under . Our team is actively working on resolving this issue. In the meantime, if you would like to contact our Sales team, please submit a ticket through our Support team here:...

2. identified 2026-08-17 21:16 UTC

   We have identified the issue causing our Contact Sales, event registration, and webinar registration forms to fail. A third-party form provider we use across our marketing site has hit a daily API limit, which is preventing new form submissions from going through. Impact is...

3. monitoring 2026-08-17 22:39 UTC

   A fix has been implemented and we are monitoring the results. Our third-party form provider has temporarily raised our API limit, and Contact Sales, webinar/event registration, ZapConnect registration, and AI Leaders Lab forms are displaying and submitting successfully again....

4. resolved 2026-08-17 22:54 UTC

   This incident has been resolved. Submissions to our Contact Sales, webinar/event registration, ZapConnect registration, and AI Leaders Lab forms are working normally again. The issue was caused by our third-party form provider’s daily API limit being exhausted by internal Zapier...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-06 09:01 UTC

   We are currently investigating an issue affecting Salesforce connections. Users attempting to add or reconnect Salesforce integrations are receiving a "Cross-org Auth flows are not supported for this external client app" error and a 400 error response. **What's Happening**...

2. identified 2026-08-06 09:48 UTC

   We have identified the root cause of the Salesforce connection failures and are actively working to resolve the issue. What Happened Our investigation identified that a recent update to the Salesforce integration caused this issue for users who were automatically migrated to the...

3. monitoring 2026-08-06 11:35 UTC

   We have rolled back the problematic update and confirmed that Salesforce connections are now working properly. What you need to do: If you experienced an error when trying to connect or reconnect Salesforce, your connection should now work. You can reconnect your connection, and...

4. resolved 2026-08-06 12:28 UTC

   We have successfully resolved the Salesforce connection issues that affected some of our customers earlier today. **What Happened** A recent update to our Salesforce integration caused authentication failures for users who were automatically migrated to the new version....

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-28 13:34 UTC

   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...

2. resolved 2026-07-28 14:43 UTC

   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...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-07-22 18:32 UTC

   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 ( ). The majority of affected Google apps...

2. resolved 2026-07-22 20:38 UTC

   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...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-22 14:19 UTC

   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.

2. monitoring 2026-07-22 16:34 UTC

   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...

3. resolved 2026-07-22 17:50 UTC

   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...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-21 13:35 UTC

   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...

2. monitoring 2026-07-21 20:29 UTC

   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.

3. resolved 2026-07-22 14:38 UTC

   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...

Excerpts are shortened. Read the full incident on Zapier's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-07-21 09:25 UTC

   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...

2. resolved 2026-07-21 12:32 UTC

   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...

Excerpts are shortened. Read the full incident on Zapier's status page.