Zapier Outage History

Started Oct 22, 2026, 02:02 PM UTC· resolved Oct 22, 2026, 02:46 PM UTC

1. investigating Oct 22, 2026, 02:02 PM UTC

   We have not identified customer impact related to the PHP vulnerabilities reported on October 21, 2026. Our security and engineering teams are reviewing potential exposure in NodeJS services and across Zapier. The assessment is ongoing. We will share further findings here as they are confirmed. Please reach out to our Support team "Support team": https://zapier.com/app/get-help if you need any help in the meantime.

2. resolved Oct 22, 2026, 02:46 PM UTC

   Our investigation into the reported PHP vulnerabilities is complete. We found no impact on Zapier services or customer data. This advisory is now closed. Security FAQ: PHP Vulnerabilities (CVE-2026-109618 and CVE-2026-109619) "1. What is this issue? Two vulnerabilities were disclosed in PHP, an open-source programming language. Both can lead to remote code execution under certain conditions. They affect PHP 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27, and 8.5 before 8.5.12. 2. Is Zapier affected? Our investigation is complete, and we found no impact on Zapier services or customer data. 3. Has customer data been affected? No. Our investigation found no impact to customer data. 4. Does this affect the Zapier WordPress integration for example? The Zapier WordPress plugin itself is not vulnerable. WordPress sites run on PHP, though, so site owners should make sure their PHP version is patched (see question 1 for the affected versions). 5. Could PHP applications I host be affected? Possibly. Applications you run yourself, including on third-party hosting platforms, may be vulnerable if they run an affected PHP version, regardless of Zapier. We recommend updating to a patched PHP version. "

Read the full incident report →

Started Oct 21, 2026, 03:21 PM UTC· resolved Oct 22, 2026, 04:22 PM UTC

1. investigating Oct 21, 2026, 03:21 PM 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 affecting delivery of these updates and assessing the scope of customer impact. If you need any assistance in the meantime, please reach out to our support team "support team": https://zapier.com/app/get-help.

2. identified Oct 21, 2026, 03:52 PM 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 calculations and triggers continue to run. We are monitoring the provider’s recovery and assessing customer impact. We do not yet have an estimated resolution time. Please reach out to our support team "support team": https://zapier.com/app/get-help if you need any help in the meantime.

3. identified Oct 21, 2026, 04:04 PM 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 and triggers continue to run. We are watching for improvements, but do not yet have an estimated resolution time. For any assistance in the meantime, please reach out to our support team here "here": https://zapier.com/app/get-help.

4. resolved Oct 22, 2026, 04:22 PM UTC

   The issue affecting real-time updates in Zapier Tables has been resolved. Collaborator changes and refreshed formula results should now appear normally. If you continue to experience issues, please contact our support team "support team": https://zapier.com/app/get-help.

Read the full incident report →

Started Oct 21, 2026, 02:10 PM UTC· resolved Oct 21, 2026, 08:22 PM UTC

1. identified Oct 21, 2026, 02:10 PM 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 Oct 21, 2026, 02:18 PM 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.

3. resolved Oct 21, 2026, 08:22 PM UTC

   Our Engineering team has confirmed the service disruption at BambooHR has been resolved and the normal service has been restored. Affected Zap runs have been replayed, and no additional action is necessary. If you still have errors or have questions, please feel free to open a ticket with our Support team at https://zapier.com/app/get-help

Read the full incident report →

Started Oct 16, 2026, 02:10 PM UTC· resolved Oct 16, 2026, 03:23 PM UTC

1. investigating Oct 16, 2026, 02:10 PM 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 Oct 16, 2026, 03:09 PM 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 users can close the Guided Template publishing window, open the created draft Zap directly in the Zap editor, and select Request to publish to submit it for approval.

3. resolved Oct 16, 2026, 03:23 PM 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 requirements remain in place. This issue is resolved.

Read the full incident report →

Started Oct 14, 2026, 09:40 AM UTC· resolved Oct 14, 2026, 10:29 AM UTC

1. investigating Oct 14, 2026, 09:40 AM 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 you need any assistance in the meantime, please reach out to our support here "here": https://zapier.com/app/get-help.

2. identified Oct 14, 2026, 09:49 AM 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 succeeding again. We are monitoring to ensure the recovery holds. If you encountered a permission error, please try the action again. If you continue to experience issues, please contact our support team "contact our support team": https://zapier.com/app/get-help.

3. resolved Oct 14, 2026, 10:29 AM 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 team "contact our support team": https://zapier.com/app/get-help. Thank you for your patience while we resolved this issue.

Read the full incident report →

Started Oct 14, 2026, 08:21 AM UTC· resolved Oct 14, 2026, 10:28 PM UTC

1. investigating Oct 14, 2026, 08:21 AM 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 Oct 14, 2026, 09:08 AM 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 the integration’s maintainers and are awaiting their response. Service has not yet been restored.

3. investigating Oct 14, 2026, 03:51 PM 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 Oct 14, 2026, 04:40 PM 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 may need to be reconnected manually.

5. resolved Oct 14, 2026, 10:28 PM 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 restored. New connections are working, and existing connections are refreshing automatically. A small number of connections may still need to be reconnected manually. Thank you for your patience while we worked through this! If you need support, you can reach us at: https://zapier.com/app/get-help.

Read the full incident report →

Started Oct 12, 2026, 08:39 AM UTC· resolved Oct 12, 2026, 10:27 AM UTC

1. identified Oct 12, 2026, 08:39 AM 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 duplicate query parameters without issue. Standard app actions for connected apps that run in Zaps are not affected. We'll update this page as soon as we have more information. If you need help, please reach out to our Support team at https://zapier.com/app/get-help.

2. monitoring Oct 12, 2026, 10:12 AM 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 evidence of data loss. If a connected app behaved unexpectedly during this window, please reach out so we can take a closer look. We’re continuing to monitor and will post a final update within 24 hours. If you need help, please reach out to our Support team at https://zapier.com/app/get-help.

3. resolved Oct 12, 2026, 10:27 AM 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 valid. Not every request was affected, and standard app actions in Zaps were not impacted. A fix was deployed on October 12 at 09:40 UTC to remove the duplicated parameters, and error rates returned to normal immediately. We’ve been monitoring since and have not identified any further impact or evidence of data loss. We’re reviewing the change that introduced this to prevent similar issues going forward. If you experienced errors during this window and still need help, please reach out to our Support team at https://zapier.com/app/get-help.

Read the full incident report →

Started Oct 09, 2026, 05:07 PM UTC· resolved Oct 12, 2026, 01:04 PM UTC

1. investigating Oct 09, 2026, 05:07 PM 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 Forms and Tables when the browser or client enforces Google Safe Browsing • Other flows that open the same file URLs in the browser may see the same warning or block What’s still working • Zaps continue to run, and server-side access to files is not affected by this flag in the same way Customer impact • Multiple customers have reported being unable to open file links; we're still assessing the total scope. We're working with our Security team on the Google flag and mitigation. We will provide another update by 10:53 AM PT / 5:53 PM UTC. If you need help, contact Support: https://zapier.com/app/get-help

2. investigating Oct 09, 2026, 07:06 PM 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, but any workflow where users open a Zapier-hosted file in the browser can run into it. We'll continue to keep you up to date on our progress and hope to have another update within 2 hours. If you need assistance, please reach out to our Support team at https://zapier.com/app/get-help

3. investigating Oct 09, 2026, 09:20 PM 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 this, but it can happen anywhere a Zapier-hosted file is opened in the browser. We'll continue to keep you up to date on our progress. If you need assistance, please reach out to our Support team at https://zapier.com/app/get-help

4. identified Oct 10, 2026, 03:16 AM 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 reviewed and lifted. We will update this page as soon as there is progress. Until then, you may still see a security warning when opening Zapier-hosted files in your browser. Zaps continue to run, and server-side file access isn't affected in the same way. If you need assistance, please reach out to our Support team at https://zapier.com/app/get-help

5. identified Oct 10, 2026, 03:50 AM 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 are functioning normally. Files passing through Zapier work normally on the system side as well. However, when opening a Zapier-hosted file link directly in your browser, you may still see the "dangerous site" warning until Google lifts the flag. We'll update this page as soon as we have news about when this flag will be removed. If you need assistance, please reach out to our Support team at https://zapier.com/app/get-help

6. resolved Oct 12, 2026, 01:04 PM 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 worked through this! If you need support, you can reach us at zapier.com/get-help.

Read the full incident report →

Started Oct 05, 2026, 06:54 PM UTC· resolved Oct 05, 2026, 07:46 PM UTC

1. investigating Oct 05, 2026, 06:54 PM UTC

   Our Engineering team is aware of an issue affecting users who sign into Zapier.com "Zapier.com": http://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 authentication is successful; however, the page can be accessed after a hard refresh or by opening a new tab. We are investigating the issue and will give another update as soon as we find the cause.

2. monitoring Oct 05, 2026, 07:42 PM 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 Oct 05, 2026, 07:46 PM 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 "zapier.com/get-help": http://zapier.com/get-help Thank you for your patience as we worked to resolve the issue.

Read the full incident report →

Started Sep 28, 2026, 12:13 PM UTC· resolved Sep 28, 2026, 01:18 PM UTC

1. investigating Sep 28, 2026, 12:13 PM 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 Sep 28, 2026, 12:40 PM 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 Sep 28, 2026, 01:18 PM 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 "Get help and support with Zapie": https://help.zapier.com/hc/en-us/articles/8496213764877-Get-help-and-support-with-Zapierr channels

Read the full incident report →

Started Sep 21, 2026, 03:30 PM UTC· resolved Sep 21, 2026, 07:27 PM UTC

1. investigating Sep 21, 2026, 03:30 PM 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. If you have any questions or need help, please reach out to our Support team at zapier.com/get-help.

2. identified Sep 21, 2026, 05:57 PM 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 runs where possible, and we'll keep this status page updated on our progress. Many thanks for your patience. Our Support team is available if you have any questions, and you can reach them at: zapier.com/get-help.

3. resolved Sep 21, 2026, 07:27 PM 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 issue in the future, implement better safeguards, and consolidate self-healing capabilities. Some Agent runs from previous days (September 18 to September 20) could not be replayed to avoid duplicate agent executions. For Agents, if you want to replay affected runs, go to your Agents dashboard: https://agents.zapier.com/bots, open the All Activity: https://agents.zapier.com/activity tab to view recent runs, and review the agent runs during the incident window. You can replay any runs that need to be reprocessed by prompting the agent in the chat to retry. For Zap runs using AI by Zapier, no action needed. Our team has successfully replayed all affected AI by Zapier runs. Many thanks for your patience while we worked through this. If you gave any questions or need help, reach out to our support team at: zapier.com/get-help.

Read the full incident report →

Started Sep 09, 2026, 05:51 PM UTC· resolved Sep 09, 2026, 07:41 PM UTC

1. investigating Sep 09, 2026, 05:51 PM 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 actively investigating and will continue to update this status page with our progress. Many thanks for your patience! If you have any questions, please contact our Support team at: zapier.com/get-help.

2. identified Sep 09, 2026, 06:14 PM 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 to our Support team at: zapier.com/get-help.

3. monitoring Sep 09, 2026, 06:59 PM 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 patience while we worked through this, and we will share a final update once all Zap runs are displaying successfully. If you have questions or need help, please contact our Support team at: zapier.com/get-help.

4. resolved Sep 09, 2026, 07:41 PM 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 "zapier.com/get-help": http://zapier.com/get-help.

Read the full incident report →

Started Sep 08, 2026, 02:06 PM UTC· resolved Sep 08, 2026, 05:08 PM UTC

1. monitoring Sep 08, 2026, 02:06 PM 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 missed webhook events where possible. If you notice a Zap that should have run during this window and did not, contact Support: zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help

2. resolved Sep 08, 2026, 05:08 PM 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: zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help

Read the full incident report →

Started Sep 01, 2026, 12:03 PM UTC· resolved Sep 07, 2026, 12:44 PM UTC

1. investigating Sep 01, 2026, 12:03 PM 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 Sep 03, 2026, 02:16 PM 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 Sep 03, 2026, 09:39 PM 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

4. investigating Sep 04, 2026, 07:08 PM 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: https://zapier.com/app/get-help

5. resolved Sep 07, 2026, 12:44 PM 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: https://zapier.com/app/get-help Thank you for your patience.

Read the full incident report →

Started Aug 28, 2026, 02:35 PM UTC· resolved Aug 28, 2026, 03:35 PM UTC

1. investigating Aug 28, 2026, 02:35 PM 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: https://zapier.com/app/get-help

2. monitoring Aug 28, 2026, 03:01 PM 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 Support: https://zapier.com/app/get-help

3. resolved Aug 28, 2026, 03:35 PM 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 folder/subfolder creation — have been verified and are working normally. No data loss occurred, and Zap runs were not affected. If you're still experiencing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience.

Read the full incident report →

Started Aug 26, 2026, 04:55 PM UTC· resolved Aug 26, 2026, 09:41 PM UTC

1. investigating Aug 26, 2026, 04:55 PM 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 Aug 26, 2026, 05:24 PM 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 is actively working to determine the root cause. We'll provide another update as soon as possible. If you need help: https://zapier.com/app/get-help

3. monitoring Aug 26, 2026, 06:59 PM 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, and we are continuing to roll it out fully. No data has been lost. We have confirmed that affected triggers replay successfully, and we are now replaying the triggers that failed during this incident. Our team is monitoring closely to confirm the issue is fully resolved. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience.

4. resolved Aug 26, 2026, 09:41 PM 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: [https://zapier.com/app/get-help](https://zapier.com/app/get-help)

Read the full incident report →

Started Aug 21, 2026, 11:48 PM UTC· resolved Aug 22, 2026, 02:19 AM UTC

1. investigating Aug 21, 2026, 11:48 PM 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 log in, please open a case with our Support team at https://zapier.com/app/get-help so we can continue to keep you up-to-date.

2. monitoring Aug 22, 2026, 01:45 AM 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 affected during the incident and will provide further updates as needed. Thank you for your patience and we appreciate you bearing with us as we worked through this. If you continue to experience any issues, please reach out to our Support team at https://zapier.com/app/get-help.

3. resolved Aug 22, 2026, 02:19 AM 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, please reach out to our Support team through this link: https://zapier.com/app/get-help.

Read the full incident report →

Started Aug 21, 2026, 09:40 AM UTC· resolved Aug 25, 2026, 02:20 PM UTC

1. investigating Aug 21, 2026, 09:40 AM 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 connections are restored. Other Zap steps and non-Salesforce workflows are not broadly affected based on what we know so far. We’re actively investigating and will provide another update within 60 minutes. If you need help, contact Support: https://zapier.com/app/get-help

2. investigating Aug 21, 2026, 10:49 AM 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: https://zapier.com/app/connections • If your Salesforce connection shows as expired or disconnected, you’re affected • Zaps that use that Salesforce connection as a trigger (especially polling triggers) may stop firing while the connection is expired • You may also see held Zap runs or trigger authentication failures in Zap History What to do Reconnect the affected Salesforce connection from My Apps. Use a Salesforce user that has permission to authorize the connection in your org. Once reconnected, polling triggers should resume on their normal schedule. Held or missed runs should begin processing again after the connection is healthy. Other impact Zap steps that do not use the affected Salesforce connection, and workflows outside Salesforce, are not broadly affected based on what we know so far. What we’re doing Re-authentication has restored service for customers who have the required Salesforce permissions. We have not deployed a platform-wide fix yet. We are investigating why these connections were invalidated and coordinating with Salesforce. We will provide another update within 60 minutes. If you need help, contact Support: https://zapier.com/app/get-help

3. resolved Aug 25, 2026, 02:20 PM 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.

Read the full incident report →

Started Aug 19, 2026, 04:07 PM UTC· resolved Aug 19, 2026, 07:36 PM UTC

1. investigating Aug 19, 2026, 04:07 PM 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

2. monitoring Aug 19, 2026, 04:39 PM 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

3. investigating Aug 19, 2026, 04:45 PM 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

4. resolved Aug 19, 2026, 07:36 PM 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

Read the full incident report →

Started Aug 18, 2026, 11:50 PM UTC· resolved Aug 18, 2026, 11:58 PM UTC

1. investigating Aug 18, 2026, 11:50 PM 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 currently migrating your Functions, you may experience disruptions until this issue is resolved. Our team is actively investigating and working to restore full functionality. If you need help, contact Support: [https://zapier.com/app/get-help](https://zapier.com/app/get-help)

2. resolved Aug 18, 2026, 11:58 PM 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 experiencing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience.

Read the full incident report →

Started Aug 18, 2026, 05:21 PM UTC· resolved Aug 19, 2026, 06:36 PM UTC

1. investigating Aug 18, 2026, 05:21 PM UTC

   We're currently investigating an issue where our Contact Sales "Contact Sales": https://zapier.com/l/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 team, please submit a ticket through our Support team here: zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help, and we'll be happy to assist and/or route you to the appropriate team.

2. identified Aug 18, 2026, 06:06 PM 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 free to create a ticket with Support (https://zapier.com/l/contact-sales), and we'll route the ticket accordingly.

3. monitoring Aug 18, 2026, 08:54 PM UTC

   We’ve deployed a fix for the issue that caused some Contact Sales forms "Contact Sales forms": https://zapier.com/l/contact-sales 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 the form, please feel free to create a ticket with Support (https://zapier.com/app/get-help), and we'll route the ticket accordingly.

4. resolved Aug 19, 2026, 06:36 PM 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.

Read the full incident report →

Started Aug 17, 2026, 08:49 PM UTC· resolved Aug 17, 2026, 10:54 PM UTC

1. investigating Aug 17, 2026, 08:49 PM UTC

   We are currently investigating an issue where our Contact Sales form is not rendering correctly under https://zapier.com/l/contact-sales. 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: zapier.com/get-help, and we'll be happy to assist and/or route you to the appropriate team.

2. identified Aug 17, 2026, 09:16 PM 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 limited to marketing-site forms — signing in, creating Zaps, and running existing Zaps are not affected. We are working with the provider to restore submissions as quickly as possible. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience.

3. monitoring Aug 17, 2026, 10:39 PM 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. Signing in, creating Zaps, and running existing Zaps were not affected at any point during this incident. We are continuing to monitor form submissions and traffic levels to confirm the fix holds. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience.

4. resolved Aug 17, 2026, 10:54 PM 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 traffic, which prevented these marketing-site forms from loading and submitting. The upstream limit has been raised, the internal traffic source has been stopped, and form submissions have been confirmed stable. Thanks again for your patience while we were working on resolving that, and if you have any questions, or are running into any other issues, please reach out to our support team: https://zapier.com/app/get-help

Read the full incident report →

Started Aug 06, 2026, 09:01 AM UTC· resolved Aug 06, 2026, 12:28 PM UTC

1. investigating Aug 06, 2026, 09:01 AM 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 Starting at approximately 09:42 CET on August 6, 2026, users have been unable to authenticate or reconnect Salesforce accounts. This issue is affecting multiple versions of the Salesforce integration. What We're Doing Our engineering team has identified a recent code change as the likely cause and we are actively working to restore functionality and will provide updates as soon as we have more information. Next Steps We will post another update within the next 30 minutes with either a resolution or a more detailed timeline. We apologize for the disruption and appreciate your patience as we work through this issue. For support inquiries, please contact our support team "support team": https://zapier.com/app/get-help.

2. identified Aug 06, 2026, 09:48 AM 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 new version. Who Is Affected Only users who were automatically migrated to the latest version of the Salesforce integration and then attempted to reconnect their Salesforce account are affected. If you have not tried to reconnect Salesforce since this morning, you may not have experienced any disruption. What We're Doing Our engineering team is deploying a fix that will resolve this issue. We have stopped further automatic migrations and are preparing to move affected users to the corrected version. What You Need to Do If you received an error when trying to connect or reconnect Salesforce, you will need to reconnect your Salesforce account once we have deployed the fix. We will send you detailed instructions on how to do this. Next Steps We will provide another update with confirmation when the fix has been deployed. We sincerely apologize for this disruption and appreciate your patience as we work to resolve this issue. For support inquiries, please contact our support team "support team": https://zapier.com/app/get-help.

3. monitoring Aug 06, 2026, 11:35 AM 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 it will be restored to active status. Next Steps We will provide another update once we have completed the fix. We sincerely apologize for this disruption and appreciate your patience as we work to fully resolve this issue. For support inquiries, please contact our support team at https://zapier.com/app/get-help.

4. resolved Aug 06, 2026, 12:28 PM 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. Customers attempting to connect or reconnect their Salesforce accounts received an error message. What We Did Our team quickly identified the root cause, stopped further migrations, and rolled back all affected users to a previous working version. We then systematically reactivated all affected Salesforce connections and replayed any impacted Zap runs to ensure no data was lost. Resolution All Salesforce connections have been restored and are now working normally. Your Zaps should resume processing automatically. If you experienced any issues earlier today, your connections are now active and ready to use. Thank You We sincerely apologize for this disruption and appreciate your patience as we worked to resolve this issue. If you have any questions or continue to experience problems, please contact our support team at https://zapier.com/app/get-help. Thank you for your continued trust in Zapier.

Read the full incident report →

Started Jul 28, 2026, 01:34 PM UTC· resolved Jul 28, 2026, 02:43 PM UTC

1. identified Jul 28, 2026, 01:34 PM 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 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.

2. resolved Jul 28, 2026, 02:43 PM 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 connecting or reconnecting Close, please retry and contact Zapier Support at: https://zapier.com/app/get-help.

Read the full incident report →

Started Jul 22, 2026, 06:32 PM UTC· resolved Jul 22, 2026, 08:38 PM UTC

1. monitoring Jul 22, 2026, 06:32 PM 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 (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.

2. resolved Jul 22, 2026, 08:38 PM 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 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.

Read the full incident report →