Zapier

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.

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.

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.

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

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.

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.

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.