Status: Resolved A fix has been deployed and we have confirmed no further failures since the rollout. Users signing up for a Teams trial from our pricing page should now receive a Teams trial with access to Teams features.

This incident is resolved.

If you're experiencing any other issues with your account, please contact Support at https://zapier.com/app/get-help.

Users who sign up for a Team trial are instead signed up for a Pro trial.

Status: Resolved We’ve confirmed the issue where the Slack “Find Message” action returns “no results” for bot messages that should match. To subscribe to updates about the issue, please contact our support team through this link: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Searches & Writes (Operational)</li>
 </ul>

Slack Find Message action is unable to find bot messages

Status: Resolved This incident has now been resolved, and all services are operating normally.

We’re working with Meta to confirm whether any missed leads will be resent or if further customer action is needed. We’ll share an update once we have more information.

Update: We’ve been advised that missed lead notifications from the affected period won’t be resent or backfilled.

We understand this may be disruptive for affected customers. To recover missed leads, customers can export a CSV or Excel file from Meta Ads Manager, import it into a Zapier Table, and use Transfer Data to send those leads through their Zap workflow:


• Meta export instructions: https://www.facebook.com/business/help/734933888443065
• Zapier Transfer Data instructions: https://help.zapier.com/hc/en-us/articles/8496274335885-Transfer-existing-data-using-a-Zap


If you need assistance, or continue to experience any further issues, please reach out to our Support team: https://zapier.com/app/get-help

Facebook Lead Ads intermittently missing leads

Status: Resolved Our Engineering team identified and resolved the issue causing degraded performance for Agents. Due to the nature of the issue, we're not able to replay Agent executions during the following incident windows

2026-06-18, between 5:47–7:15PM UTC
2026-06-18, between 8:32 PM–10:08 PM UTC

Affected users have been notified via email

The incident has been resolved, and Agents is now operating as expected. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Degraded performance for Zapier Agents

Status: Resolved This incident has been resolved. Earlier today, webhook-based triggers experienced processing delays when an unusually high volume of traffic from a third-party integration overwhelmed our shared trigger-processing system. As a result, trigger events across a range of apps were processed more slowly than usual, with delays peaking at around five minutes.

We increased our processing capacity to clear the backlog, and the third-party integration also applied mitigations on their end to reduce the excess traffic. Trigger processing has returned to normal and our systems are fully operational.

No trigger data was lost during the incident — affected events were delayed rather than dropped, and all delayed events have now been processed.

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

Thanks again for your patience while we were working on resolving that. Affected components
 <ul>
 <li>Instant Triggers (Operational)</li>
 </ul>

Delayed processing for webhook-based triggers

Status: Resolved We have successfully resolved the Facebook Lead Ads integration issue that affected our platform from 12:30pm–4:00pm PDT (7:30pm–11:00pm UTC) on June 16, 2026.

During this window, customers experienced failures when connecting or reconnecting Facebook Lead Ads and Facebook Pages integrations, and existing Zaps using these integrations failed to execute. We identified this as an upstream issue with Facebook's APIs, which has since been resolved.

All affected workflows have been replayed and are now operating normally. If you continue to experience any issues with your Facebook integrations, please try reconnecting your Facebook app connection or don't hesitate to contact Zapier Support: https://zapier.com/app/get-help.

Error connecting to Facebook Apps

Status: Resolved The issue affecting access to Zapier template pages has been resolved. Users should now be able to access template pages as expected.

We’ve made improvements to help prevent this from happening again and will continue monitoring for stability.

If you continue to experience issues accessing templates, please don't hesitate to contact Zapier Support: https://zapier.com/app/get-help. Affected components
 <ul>
 <li>Website (Operational)</li>
 </ul>

Intermittent errors loading Zapier Templates pages

Status: Complete We have successfully completed the scheduled maintenance on our Tables service. The upgrade of our underlying database infrastructure is now complete, and all systems are operating normally.

Maintenance Summary:

• Maintenance window: 4:00 PM - 6:15 PM CET on Saturday, June 13, 2026
• All database instances have been upgraded and are running the latest version
• Full functionality has been restored

What to Expect: Your Tables service is now fully operational. If you experienced any transient errors or slowness during the maintenance window, these have been resolved. All table operations, including sorting, filtering, and data export, are working as expected.

Thank You: We appreciate your patience during this maintenance window. This upgrade improves the performance and stability of our Tables infrastructure for all users. If you have any questions or encounter any issues, please contact our support team.

We're back to normal operations. Thank you for your understanding. Affected components
 <ul>
 <li>Polling Triggers (Operational)</li>
 </ul>

Maintenance: Scheduled Infrastructure Maintenance

Status: Resolved The issue preventing some users from loading templates is now resolved, and templates are loading normally.

 If you’re still experiencing issues, please contact Support: http://zapier.com/app/get-help Affected components
 <ul>
 <li>Website (Operational)</li>
 </ul>

Templates not loading

Status: Resolved Between June 9 and June 11, some webhook-triggered Zap runs experienced processing delays of up to 48 hours.

All delayed events have since been processed successfully, and no data was lost during this delay. We are implementing additional safeguards to prevent recurrence.

If you experience any ongoing issues, contact Support: https://zapier.com/app/get-help

Thank you for your patience. Affected components
 <ul>
 <li>Instant Triggers (Operational)</li>
 </ul>

Delayed webhook Zap runs

Status: Resolved The issue affecting Chatbots has been resolved.

Between approximately 11:00 PM and 5:30 AM MST on June 8, 2026, some customers may have experienced failures or timeouts when initializing chats or interacting with embedded chatbots. The issue self-resolved and Chatbots has been operating normally since.

Zap Runs and tasks were not affected. No data loss occurred.

We are continuing to monitor the service and will take steps to reduce the likelihood of recurrence.

If you experienced issues during this window or notice anything still not working, contact Support: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Chatbots (Operational)</li>
 </ul>

Chatbots dropping connections; possible "Forbidden" errors

Status: Resolved The issue affecting Zapier Templates pages has been resolved.

Some users may have experienced intermittent errors or missing content when loading Templates pages. We’ve taken steps to stop the abnormal traffic driving the problem, and the Templates pages are now operating normally.

If you’re still seeing issues, please contact Support: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Website (Operational)</li>
 </ul>

Intermittent errors on Templates pages

Status: Resolved A fix has been implemented, and after some monitoring, we're no longer seeing errors when customers are requesting Zap History exports. Any previous export requests during the incident window below have been successfully replayed, so no action is needed.

Jun 5th 2026 13:42 - 19:00 UTC


If you're still having issues or have questions, please reach out to our Support team at https://zapier.com/app/get-help Affected components
 <ul>
 <li>Zap History (Operational)</li>
 </ul>

Zap History Export Notifications are not being send to users.

Status: Resolved Shopify Service Restored

We're pleased to report that Shopify's services have fully recovered and are operating normally. Our Shopify app is now functioning as expected, and Zap triggers and actions are executing successfully.

What happened

Between approximately 13:06 UTC and 15:28 UTC on June 3rd, Shopify experienced a widespread outage affecting their Admin API, GraphQL endpoints, and multiple other services. This caused failures in both Zap triggers and Zap actions that rely on Shopify integrations.

What we did

Once Shopify's services were restored, we automatically replayed all impacted Zap runs to ensure your workflows could complete successfully. Any remaining failed runs will be handled by our automatic replay system. No further action is required from you.

We've completed our investigation and confirmed all systems are stable. If you experience any further issues with your Shopify integrations, please don't hesitate to reach out to our support team.

Thank you for your patience during this incident.

Shopify Service Disruption

Status: Resolved This incident has been resolved.

The issue that was causing some Code by Zapier steps to fail with the environment variable error has been fixed, and Code by Zapier is now operating normally. Any tasks that were affected during the disruption have been replayed, so no action is needed on your end.

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

Thanks again for your patience while we working on resolving that.

Code by Zapier is running into Lamda errors mentioning KMS

Status: Resolved We have been able to confirm that the update we previously pushed has fully resolved that error. So your Code by Zapier steps should be working as normal, and no longer running into those errors.

 

We are also working on automatically replaying affected Zap runs that were running into this issue.

If you are running into this error, please reach out to our support team: https://zapier.com/app/get-help

Thanks again for your patience while we resolved that.

Code by Zapier seeing errors

Status: Resolved This issue has been resolved. The delays between Zap execution and when runs become visible in Zap History are no longer occurring. Zap History data should now be appearing in the UI as expected.

As noted in our earlier update, Zap executions themselves were not impacted — this issue only affected the visibility of run data in the UI.

Thank you for your patience while our team worked on this. If you continue to experience any issues, please don't hesitate to contact support: https://zapier.com/app/get-help

Delays between Zap execution

Status: Resolved The issue causing Code by Zapier steps to return "No response from child process" errors has now been fully resolved.

What happened

Starting at 14:00 UTC on May 20th, Code by Zapier steps began failing with "No response from child process" errors.

Resolution

Our engineering team identified the root cause, due to a recent change that routed Team plan Code Steps through a new system. After our team disabled this change, error rates dropped significantly and we have not seen new occurrences since this change.

Impact

The incident lasted approximately 3 hours and 28 minutes (14:00–17:28 UTC). All affected tasks have been replayed and are now executing successfully. No data was lost, and no action is needed on your side for these runs directly.

We apologize for the disruption and appreciate your patience while we resolved this issue. If you do see any further issues with any code steps on your account, please reach out to our team at https://zapier.com/app/get-help Affected components
 <ul>
 <li>Instant Triggers (Operational)</li>
<li>Searches & Writes (Operational)</li>
<li>Polling Triggers (Operational)</li>
 </ul>

Code Steps failing with "No response from child process" across Zaps/APIs

Status: Resolved The issue affecting our LinkedIn, LinkedIn Conversions, and LinkedIn Lead Gen Forms integrations has been resolved.

Earlier today, an upstream LinkedIn API incident caused intermittent authentication and connection errors. LinkedIn’s platform has recovered, our internal error rates are back to normal, and we’ve replayed impacted tasks where needed.

LinkedIn and LinkedIn Ads integrations should be working normally again. If you still see errors, retry your connection or Zap task.

If you need help, contact Support: https://zapier.com/app/get-help

LinkedIn Integrations— authentication and connection errors

Status: Resolved The issue preventing some enterprise customers from managing custom actions has been resolved.

Customers with over 100 app restrictions were unable to paginate through their custom actions due to a URL formatting issue in our system. This has been corrected and all affected pages now load as expected.

No data was lost and no customer action is required.

If you're still experiencing issues, contact Support: https://zapier.com/app/get-help

Thank you for your patience.

Customer with a large number of app restrictions cannot manage custom actions.

Status: Complete Successfully completed maintenance. Polling-based triggers have resumed. Missed polls should be picked up. Affected components
 <ul>
 <li>Polling Triggers (Operational)</li>
 </ul>

Maintenance: Scheduled: Infrastructure Maintenance

Status: Resolved Between approximately 1:20 AM UTC and 10:38 AM UTC on May 13, 2026, Zaps using Facebook Lead Ads experienced failures due to an upstream issue with Meta’s Facebook Lead Ads API.
During this time, Facebook Lead Ads Zaps were unable to process new leads. Some Zaps may have been automatically turned off due to repeated errors.
Meta has resolved the issue on their end, and error rates have returned to normal. Your Zaps should now be functioning as expected, and new leads from Facebook will resume flowing through normally.
Zaps that were automatically turned off have been re-enabled, and failed runs have been replayed.
If you’re still experiencing issues, contact Support: https://zapier.com/app/get-help

Facebook Lead Ads Error: "Unsuported get request. Object with ID "..." does not exist, cannot be loaded due to missing permissions or does not support this operation"

Status: Complete We have successfully completed the scheduled maintenance. All systems are operational. Affected components
 <ul>
 <li>Login (Operational)</li>
 </ul>

Maintenance: Scheduled platform upgrade

Status: Resolved Our Engineering team has monitored our backend for any spikes in errors after the fix was released, and we're happy to see that we're at normal operation and no longer seeing errors.

As such, the incident is now considered resolved. Please reach out to our Support team if you continue to see issues or have questions about the incident.

Errors when creating or reconnecting app connections

Status: Resolved The issue has been resolved, and all systems are back to normal.

High Latency is impacting hook ingestion

Status: Resolved The issue causing incorrect “High Error Ratio” notifications has been resolved.

Impact
 Some users received an email titled “High Error Ratio” indicating their Zap would be switched off. In certain cases, this did not reflect actual Zap performance, and some Zaps may have been paused incorrectly as a result.

Resolution
 We implemented a fix and confirmed that notifications and Zap status are now behaving as expected.

If you are still experiencing this issue causing your Zaps to turn off, you can reach out to our team at: https://zapier.com/app/get-help. Affected components
 <ul>
 <li>Zap History (Operational)</li>
 </ul>

Zap error notifications

Status: Resolved Our team has confirmed that since 21:14 UTC all customers logging into Zapier via Google SSO can do so successfully. If you are still running into any issues, please contact our support team for assistance: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Login (Operational)</li>
 </ul>

Google SSO Login Failures

Status: Resolved The issue causing 522 timeout errors with the Klaviyo app integration has been resolved. This was related to an upstream service disruption on Klaviyo's side: https://status.klaviyo.com/incidents/yyh7s59brj67

Zaps using Klaviyo should now be functioning as expected. No data loss occurred — any Zap runs that failed during the incident can be replayed from Zap History.

If you are still experiencing issues with your Klaviyo integration, please contact Support: https://zapier.com/app/get-help

Thank you for your patience.

Errors related to Klaviyo app integration

Status: Resolved We’ve resolved an issue where some users could see a “Session initialization failed” error when creating new app connections. The issue was caused by an unintended staged rollout configuration and was mitigated by rolling back the rollout.

Existing Zaps and workflows were not impacted. If you saw a failed connection attempt during the incident window, please retry creating the connection now.

If you’re still experiencing issues creating new app connections, please contact Zapier Support.

Session initialization failed error when trying to connect apps

Status: Resolved We've implemented an update so webhooks sent with a Content-Type header that specified a non-UTF-8 character set will trigger your Zaps.

Incoming webhooks — some requests not processed (encoding in Content-Type)

Status: Complete The scheduled maintenance on Zapier Tables has been successfully completed. All services are now operating normally.

Thank you for your patience. If you continue to experience any issues, please don’t hesitate to reach out to support. Affected components
 <ul>
 <li>Tables (Operational)</li>
 </ul>

Maintenance: Zapier Tables maintenance

Status: Resolved No additional customer reports have been received during the monitoring period. The incident is ready to be closed. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

INC-908: Firecrawl outage

Status: Resolved The performance issues that caused delays and timeouts on Zapier.com "Zapier.com": http://Zapier.com have now been resolved. Our systems have remained stable, and signing in, loading account information, and running Zaps should behave normally.
During the incident, some customers may have seen slower responses, failed actions, or delayed trigger processing while we reduced load and shipped the fix. Everything should now be caught up; if you still see anything unexpected, try running your Zap again.

If you need help with a specific Zap or account, contact our Support team: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Website (Operational)</li>
<li>Login (Operational)</li>
<li>Support (Operational)</li>
 </ul>

Service delays and timeouts across Zapier.com

Status: Resolved We can confirm that the Admin Center is now loading as expected, and the issue is now resolved. If you're still unable to load the page, you may need to reload the page and/or clear your browser's cookies and cache.

If you're experiencing any issues with this was not resolved by clearing browser cache and cookies, please reach out to our support team here: https://zapier.com/app/get-help

Users are unable to access Admin Center.

Status: Resolved The issue preventing ownership transfer in Teams and Enterprise accounts has been resolved. Account ownership transfers can now be self-served by following this guide: https://help.zapier.com/hc/en-us/articles/17946190203789-How-to-transfer-ownership-of-your-Team-or-Enterprise-account

If you're experiencing any issues with this, please do reach out to our support team here: https://zapier.com/app/get-help

"Unable to verify identity. Please try again." Error when transferring ownership between Team members.

Status: Resolved The issue affecting invoice access and downloads has been resolved. Service was fully restored at 18:30 UTC on April 27, 2026.

At 17:20 UTC an outage from the Databricks App caused invoices to fail to load or download from the Billing and Invoices Page. Databricks released a fix for their outage and invoices are functioning as normal. If you attempted to view or download any invoices during this time, you can retry that action now.

We apologize for the inconvenience this caused and appreciate your patience while the issue was resolved.

If you have any questions, please reach out to our Support Team - https://zapier.com/app/get-help Affected components
 <ul>
 <li>Website (Operational)</li>
 </ul>

500 error when viewing upcoming invoices

Status: Complete The maintenace is now complete. Affected components
 <ul>
 <li>Developer Platform (Operational)</li>
 </ul>

Status: Resolved The issue causing some AI by Zapier steps to fail with a 500 error when adding a knowledge source has been resolved.

If you were affected by this issue, your Zaps with AI by Zapier steps using knowledge sources will now work again. To restore functionality:


1. Open the affected Zap and navigate to the AI by Zapier step
2. Before deleting the step, we recommend copying and saving your prompt to avoid losing any work.
3. Delete the step
4. Re-add the AI by Zapier step
5. Copy your previous prompt into the new step
6. Re-upload your knowledge sources


Once you've completed these steps, your Zap will be ready to use.

If you are experiencing this issue, you can connect with our support team here: https://zapier.com/app/get-help.

AI by Zapier action Fails with 500 error when a Knowlledge source is added

Status: Resolved The issue affecting chatbot users has been resolved. Chat completion features are now functioning normally, and users should no longer encounter error messages when interacting with chatbots.

Chatbot

Status: Resolved We have successfully resolved the chatbot availability issue that affected some of our users. Our engineering team identified and resolved the underlying authentication issue.

All chatbot services are now operating normally. You should now be able to view and manage your chatbots in the dashboard and use them externally without any issues. We have monitored and verified that the service is working properly.

We apologize for any disruption this may have caused. If you experience any further issues accessing your chatbots, please contact our support team: https://zapier.com/app/get-help. Affected components
 <ul>
 <li>Chatbots (Operational)</li>
 </ul>

Chatbots failing to load

Status: Resolved We confirm that the fix deployed has resolved the issue with Agents and Canvas, and both are functioning correctly. All Agent workflow executions that were stuck on 'In Progress' status during this incident have been replayed.

If you are experiencing any issues with Zapier Agents or Canvas, please contact our support team through this link: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Agents (Operational)</li>
<li>Canvas (Operational)</li>
 </ul>

agents.zapier.com is down

Status: Resolved This incident is fully resolved. Customers can now create Chatbots and Forms as usual. 

Many thanks for your patience, and feel free to reach out to our support team if you have any questions at: zapier.com/get-help. Affected components
 <ul>
 <li>Forms (Operational)</li>
<li>Chatbots (Operational)</li>
 </ul>

Creation of new chatbots and forms results in an error

Status: Resolved We have resolved the issue with web-scraping tools not working throughout tools like Agents, Chatbot knowledge sources, and Web Parser.

For any questions, or if you're still seeing failures with web-scraping tools in Zapier, please contact: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Chatbots (Operational)</li>
<li>Agents (Operational)</li>
 </ul>

Web-scraped sources cannot be added to Chatbots, and Agents not returning informatio

Status: Resolved We have been able to get this issue resolved.

Users should now be able to successfully download their Zap Run History export files.

If you are running into any other issues, feel free to reach out to Zapier Support: https://zapier.com/app/get-help

Zap Run History Export Download Links Returning Errors

Status: Resolved The connectivity issue which affected Zapier Agents during a 15 minute window is fully resolved. Agent executions are back to normal, and connectivity remains stable.

If you have any questions, please reach out to our support team at: zapier.com/get-help. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Temporary Agent run executions errors during a 15-minute window

Status: Resolved The issue causing 404 errors when editing and deleting Zap templates has been resolved.

Users attempting to edit templates were encountering 404 errors due to a routing misconfiguration introduced during an ATC (Application Traffic Control) rollout, which changed the default ATC origin from the monolith to the marketing site. This broke routing for the /zap-templates path, causing edit actions to fail.

The fix was deployed by completing the ATC routing correction to production. Once the rollout completed, edit functionality was restored. A remaining cosmetic bug — where the UI incorrectly indicates a template deletion failed despite the deletion succeeding — has been identified as a separate, no-impact bug and does not affect actual data.

No data was lost as a result of this incident.

If you're still experiencing issues, please contact Support by clicking above or visit: https://zapier.com/app/get-help

Thank you for your patience.

404 Errors while editing templates

Status: Resolved We have successfully resolved the intermittent delays affecting Slack-triggered Zaps that began around Friday, April 11th. Our engineering team identified and deployed a fix, and Slack triggers are now operating as expected.

If you continue to experience any delays with your Slack-triggered Zaps or have any questions, please don't hesitate to contact our support team at https://zapier.com/app/get-help

We appreciate your patience while we worked through this issue.

Is Zapier down?

Zapier status is UP

Lastest published events

Users who sign up for a Team trial are instead signed up for a Pro trial.

Slack Find Message action is unable to find bot messages

Facebook Lead Ads intermittently missing leads

Zapier Services, Components and Regions

Recent Zapier events

Users who sign up for a Team trial are instead signed up for a Pro trial.

Slack Find Message action is unable to find bot messages

Facebook Lead Ads intermittently missing leads

Degraded performance for Zapier Agents

Delayed processing for webhook-based triggers

Error connecting to Facebook Apps

Get your FREE account now,
5 monitors included!

Is Zapier down?

Zapier status is UP

Lastest published events

Users who sign up for a Team trial are instead signed up for a Pro trial.

Slack Find Message action is unable to find bot messages

Facebook Lead Ads intermittently missing leads

Zapier Services, Components and Regions

Recent Zapier events

Users who sign up for a Team trial are instead signed up for a Pro trial.

Slack Find Message action is unable to find bot messages

Facebook Lead Ads intermittently missing leads

Degraded performance for Zapier Agents

Delayed processing for webhook-based triggers

Error connecting to Facebook Apps

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!