Zapier

We are currently investigating a spike in errors affecting Facebook Lead Ads integrations. Users may experience failures when running Zaps connected to Facebook Lead Ads, with errors related to missing permissions or unsupported requests. Our integrations team is actively investigating the root cause and working toward a resolution. We will provide updates as soon as we have more information.

We are currently investigating an issue where users may encounter the following error when creating a new connection or reconnecting an app: "Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'. Uh oh, something is not quite right!" Our team is actively working to identify the root cause. We’ll provide updates as soon as more information is available.

We are currently investigating an issue causing elevated latency in hook ingestion and event processing. As a result, some customers may experience delays of approximately 30–40 minutes before events are processed. Our team is actively working on the fix.We appreciate your patience and understanding while we work to resolve this issue.

We are currently investigating an issue impacting Google single sign-on (SSO). Users attempting to log in to their zapier.com account using Google SSO may be unable to authenticate at this time. Impact All users are affected when using Google SSO. Login via username and password remains available, and users with active sessions are not impacted. Running automations continue to operate normally. Current Status Our engineering team is actively investigating the root cause. Initial efforts are focused on reviewing Google SSO configuration, credentials, and related environment variables. Relevant teams have been engaged and are working to identify and resolve the issue as quickly as possible. We will provide further updates as more information becomes available.

We’re investigating an issue affecting some Zaps that use error handling. You may have received an email titled “High Error Ratio” explaining that your Zap would be switched off. In some cases, that may not have matched what you see in normal use, and your Zap may have been paused as a result. We’re working on a fix to prevent this from happening again. If that happened to your Zap, you can turn it back on from your Zapier dashboard. We’ll post another update here when we have more to share.

We are currently investigating an issue where users receive "Session initialization failed" errors when attempting to connect apps in Zapier.

We are looking into an issue related to the Klaviyo app returning 522 timeout errors. This is related to an incident with Klaviyo here: https://status.klaviyo.com/incidents/yyh7s59brj67

Between April 26, 2026, 7:14 PM UTC and April 30, 2026, 4:36 AM UTC, a subset of incoming webhooks to Zapier were not processed during ingestion. Webhooks sent with a Content-Type header that specified a non-UTF-8 character set in the way below were rejected instead of being delivered to your Zaps: Content-Type: application/x-www-form-urlencoded; charset=iso-8859-1 Webhooks using typical UTF-8 Content-Type values were not affected by this issue. If your upstream system sent webhooks matching the pattern above during that time window, those individual events did not trigger your Zaps. Other triggers and webhook formats continued to work as usual. For any specific events that occurred while your app was sending webhooks in that format during the window above, you will need to resend the webhook from the upstream application (for example, by having that app fire the event again or resubmit the payload), so that Zapier receives a new request. Replaying a past run in Zapier does not replace a missing inbound webhook from your app. If you are unsure whether your integration uses that header, check your server or integration configuration for charset=iso-8859-1 (or other non-UTF-8 charset) on application/x-www-form-urlencoded requests to your Zap’s webhook URL.

At approximately 4:45 AM UTC we experienced degraded performance affecting agents web search and chatbot website knowledge-source syncing due to an outage at our third-party provider, Firecrawl. Firecrawl has recovered and our services are operating normally again. Most affected runs recovered automatically, but a subset of agent runs may have failed during the incident window—customers can check their Activity and retry failed runs if needed. We’re continuing to monitor for any residual errors and will provide an update before closing.

Users are unable to access the Admin Center within Zapier settings. This controls access to SSO, SCIM, app connections, and other user management settings. The Admin Center page does not finish loading, but doesn't show an error otherwise Our Engineering team has confirmed the issue and is working toward resolving the problem as soon as possible.

We’re seeing delays and timeouts affecting parts of Zapier. Our team is investigating and working to restore normal performance. What you might notice Slower responses or failed actions in places that depend on signing in or loading account information. Some Zaps and background tasks may also run more slowly or time out. Experiences that use AI or chat-style features may also be affected. What we know Our systems are under a heavier load than usual. We’ve narrowed the problem to unusually high demand on account-related requests and are working to confirm what’s driving it and how to safely reduce the load. What we’re doing We’re focused on stabilizing performance and will share more as we have concrete progress. Next update We expect to post another update within about 30 minutes. We’re sorry for the trouble this causes and thank you for your patience. Questions? Contact our Support team: https://zapier.com/app/get-help

Users have reported that transferring ownership between Team members returns the following error. Unable to verify identity. Please try again. Our Engineering team is looking into the issue and working to identify the root cause. We'll continue to update you as we have more information.

We're currently investigating an issue where loading upcoming invoices on the billing page can return errors (HTTP 500) instead of showing invoice details. We will update the page as soon as we have more information. If you have any questions, please reach out to our Support Team - https://zapier.com/app/get-help

We are investigating an error related to AI by Zapier when adding a knowledge source. If you are experiencing this issue, you can connect with our support team here: https://zapier.com/app/get-help

We are currently investigating an issue affecting chatbot users. Users are unable to use chat completion features, and all interaction attempts are resulting in the following error message: “There is a temporary issue with OpenAI: Attempted to access resource with incorrect regional hostname. Please make your request to api.openai.com "api.openai.com": http://api.openai.com” Our engineering team is actively working to identify the root cause and implement a solution. We will provide updates on this status page as progress is made. If you are experiencing issues or need assistance, please contact our support team: https://zapier.com/app/get-help

We are currently investigating an issue that is preventing some customers from accessing their chatbots. Affected users have reported seeing "Unable to load Chatbot" errors when attempting to view or manage their chatbots. We are looking into the cause of this issue and will update this status as soon as possible.

agents.zapier.com "agents.zapier.com": http://agents.zapier.com is down and not responding. The websites are inaccessible for all users. We are looking into the cause of this issue and will update this status as soon as possible.

Our team has identified an issue affecting Chatbot and Forms creation. Existing Forms can be edited normally. For Chatbots, users might see an error when updating the slug as well. The Engineering team is working on a fix, and we'll be updating this status page shortly once resolved.

Due to a third party outage, we are investigating an outage causing failures for chatbot users attempting to add new knowledge sources that require web-scraped knowledge sources. Existing knowledge sources for Chatbots remain functional. Agents executions do not crash, or get marked as failed, but users may get a bad response when web browsing/scraping. There are not user facing errors for this behaviour. Main error periods: 19:18–19:35 UTC and 21:35–22:32 UTC. Errors began around 19:19UTC, and subsided after 22:32 UTC, and monitoring shows no new failures. If you need help or have any questions, please contact Support: https://zapier.com/app/get-help

We have identified an issue where links to access Zap data exports are returning errors and are temporarily inaccessible. Users who attempt to access a previously generated Zap export link may be unable to do so at this time. We will provide an update within the next 2 hours (3 PM PST).

We have identified an issue that affected Zapier Agents during a 15-minute window between 9:00AM-9:15AM EST, due to a temporary connection failure. A fix has been implemented and Agent runs are executing successfully. We will continue to monitor the service to confirm resolution.

We are currently investigating 404 errors while editing zap templates. Our engineering team is actively investigating the root cause and exploring solutions. We'll update this status page as we make progress toward a resolution. If you're experiencing issues or need assistance, please contact our support team at https://zapier.com/app/get-help