Status: Resolved Copilot "Ask" mode is up and running again and and can be utilized for all accounts.

Earlier today the "Ask" mode was malfunctioning, causing repeated prompts, duplicate messages, and eventual crashes when users attempted to build Zaps.

If you experience ongoing issues, contact Support by clicking above or go to: https://zapier.com/app/get-help

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

Copilots "Ask" mode is not working correctly

Status: Resolved We've identified and resolved the soft timeout limit errors that were impacting Code by Zapier and Custom Action steps. This issue was affecting the execution and processing of these steps across multiple Zaps. All affected runs have been automatically replayed.

If you experienced any issues or need additional support, please feel free to reach out at https://zapier.com/app/get-help

Errors related to Custom Actions and Code by Zapier steps

Status: Resolved This issue has been resolved, and agent executions are operating normally.

Between April 6, 2026, at 22:12 UTC and 22:47 UTC, a dependency that powers Agents became unavailable due to internal load test traffic.

Agents triggered during this window may have failed to execute and will not be automatically retried. Agents that run from a Zap have been replayed and succeeded as well.

If an agent run failed during this window, re-run the agent (or trigger it again via its normal trigger mechanism). New executions should now succeed.

We apologize for the disruption. If you’re still seeing the issue, please refresh and try again, or contact Support at https://zapier.com/app/get-help. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Intermittent agent execution failures

Status: Resolved The incident affecting some custom action steps has been resolved.

Between 22:12 and 22:47 UTC on April 6, 2026, some customers experienced failed or delayed workflow executions when using custom actions.

Systems are stable and we’ve successfully replayed impacted Zap runs. Thanks for your patience.

Delayed or failed custom action requests

Status: Resolved We've identified and resolved the root cause of the functions outage.

The issue has been resolved and systems are operating normally.

The team will continue to monitor performance and ensure full recovery across all impacted users. Affected components
 <ul>
 <li>Functions (Operational)</li>
 </ul>

Functions not executing

Status: Complete The maintenance is now complete. Affected components
 <ul>
 <li>Tables (Operational)</li>
 </ul>

Maintenance: Zapier Tables maintenance

Status: Resolved resolved Affected components
 <ul>
 <li>Functions (Operational)</li>
 </ul>

Update PostgreSQL from version 14 to 17.

Status: Resolved Our team has resolved the issue, and connections can now be established again.

Facebook Lead Ads and Microsoft apps are returning 'Cache key will cause errors if used with memcached' errors when creating new connections

Status: Resolved This is now resolved. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Zapier Agents - Webhook triggers showing a placeholder URL

Status: Resolved We’ve resolved an issue where adding certain knowledge sources in Zapier Agents could get stuck on a loading spinner. A fix has been deployed to production and verified.

If you’re still seeing the issue, please refresh and try again, or contact Support at https://zapier.com/app/get-help Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Zapier Agents - Adding a knowledge source modal is stuck on a loading spinner

Status: Resolved We’ve resolved the issue causing intermittent Internal Server Errors (HTTP 500) for some Enterprise customers when editing Zaps that use app approvals.

Our teams implemented a fix and confirmed recovery. If you continue to experience issues editing affected Zaps, please contact support. https://zapier.com/app/get-help Affected components
 <ul>
 <li>Zap Editor (Operational)</li>
 </ul>

Internal Server Errors (HTTP 500) affecting Zaps

Status: Resolved We’ve resolved the issue related to Zaps that were paused during a prior authentication incident.

Some Zaps were automatically paused as a protective measure during an earlier incident "an earlier incident": https://status.zapier.com/incidents/01KMZFA6V1H9WP71FD7XZ8MP4A and did not automatically resume afterward. We investigated and confirmed the scope, and provided guidance directly to affected customers on how to review and restore any impacted Zaps.

If you believe you may have been impacted, please review any paused Zaps and re-enable them as appropriate.

And as always, Our support team is available if you have questions or need help getting workflows running again. If this is the case, or if you have any other questions please let us know at https://zapier.com/app/get-help

Zaps Paused due Prior Connection Failure with Google Services

Status: Resolved TLDR: A production upgrade for Monolithdb from version 8.0.40 to 8.4.8 is currently resolved now and everything is functional.
All systems are back to normal

Database Upgrade

Status: Resolved We have successfully completed the recovery process for the intermittent task failures that occurred between March 24-26, 2026. Our team replayed all affected tasks, which have been successful with no data loss.

**What Happened**
Between March 24 at 11:02 AM UTC and March 26 at 2:04 PM UTC, some tasks failed for customers using Zaps that depend on our developercli service.

**Resolution**
We fixed the underlying issue causing this failure and completed a full replay of all impacted tasks. No action is needed on your side if affected — tasks have been automatically recovered and are now running normally.

Thank you for your patience while we worked through this issue. If you do have any other questions or see any issues, please reach out to our Support team at zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help Affected components
 <ul>
 <li>Zap History (Operational)</li>
 </ul>

Intermittent failures across tasks due to exhausted db connections for developercli

Status: Resolved Earlier, a script error unintentionally detached saved payment methods for some active customers. This caused increased payment errors and prevented some customers from completing checkout, renewing subscriptions, upgrading plans, or paying invoices.

We worked with Stripe to reattach impacted customers’ payment methods in bulk, including a final batch for any remaining affected accounts. Payment processing has resumed and our monitoring indicates payment error rates and invoice processing are back to normal.

If you’re still having trouble making a payment, please contact Support: https://zapier.com/app/get-help

Payment failures for some customers

Status: Resolved We’ve completed our review of the publicly reported LiteLLM package issue. Zapier was not affected.

Our review confirmed that the LiteLLM versions used in our environments were not among the publicly reported impacted versions, and we found no evidence of unauthorised access or impact on customer data, Zapier systems, or services.

We will continue to monitor for any new information and will share updates if anything changes.

If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help.

Monitoring a publicly reported LiteLLM package issue

Status: Resolved We’ve deployed a fix for the issue that prevented some users from adding or removing tools on Zapier MCP servers, and we’ve confirmed the issue is resolved.

We apologize for the disruption and appreciate your patience as we got this resolved.

If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help Affected components
 <ul>
 <li>MCP (Operational)</li>
 </ul>

MCP Servers: Issues adding/removing tools

Status: Resolved Resolved - We have confirmed that the issue causing a blank OAuth Authorization page on zapier.com "zapier.com": http://zapier.com and during new connection setup has been fully resolved. If you run into any issues, please reach out to us here: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Website (Operational)</li>
 </ul>

OAuth Authorization Page Is Blank

Status: Resolved This issue has now been resolved, and all Zap runs should now be appearing correctly in the Zap history without delay.

We apologize for the disruption and appreciate your patience as we got this resolved.

If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help

Delay in Zap History displaying Zap Runs

Status: Resolved We've resolved an issue causing connection/authentication failures across Google Sheets, Google Drive, and Google Docs integrations.

A recent deployment introduced a change to Google authentication fields, which led to widespread refresh/stale authentication errors. This also had an impact on Agents and MCP workflows that use these Google integrations.

All impacts have been mitigated, and authentication error rates have returned to baseline.

If you're still seeing issues, re-check your workflows and reconnect your Google account if prompted. We also recommend reviewing your Zap history for any gaps during the incident window, especially for high-volume or business-critical workflows. If you identify missing data, you can re-process it by replaying the affected tasks in your Zap history or using Transfer to backfill: Transfer existing data using a Zap "Transfer existing data using a Zap": https://zapier.com/help/manage/history/transfer-existing-data-using-a-zap.

For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Connection Failure with Google Services

Status: Resolved The Zap History and Task Usage pages are now loading normally again. During this incident, you may have experienced slow load times, intermittent errors, or missing data on the Zap History and Task Usage pages. Zap executions were not affected and continued to run as expected throughout.

This issue is now considered resolved, and we are continuing to monitor to ensure stability.

If you're still seeing delays or errors on these pages, we recommend clearing your browser's cache and cookies and logging back into Zapier. For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help.

Delay in loading Zap History and Task Usage

Status: Resolved The checkout page payment and tax modals are now functioning normally again. During this incident, you may have been unable to add or update payment or tax information during checkout.

If you still have trouble updating payment or tax details, you can update your payment method from the billing settings page and then return to checkout.

We apologize for the disruption and appreciate your patience as we got this resolved. If you do see any further issues, please reach out to our support team at https://zapier.com/app/get-help

Checkout page not rendering properly

Status: Resolved We're seeing error levels back to a normal level with no spikes over the last 20 minutes. As such, this issue is now considered resolved.

If you still see the error messages, we recommend clearing Copilot chat by selecting the Settings icon at the top of the Copilot chat window. If that does not work, clear your browser's cookies and cache and then log back into Zapier.

For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help

Copilot intermittently not responding in the Editor

Status: Resolved Our Engineering team has decided to close this incident, as the root cause appears to be Claude's handling of MCP tool calls with Cowork. We have notified the Anthropic team of the issue and will continue working with their Support and Engineering teams to help resolve it.

If you're still running into issues or have questions, we recommend reaching out to Anthropic support by using this Help Center guide: https://support.claude.com/en/articles/9015913-how-to-get-support Affected components
 <ul>
 <li>MCP (Operational)</li>
 </ul>

Degraded Performance for Zapier MCP in Claude CoWork

Status: Resolved Thank you for your patience as we worked to resolve the issue.

We're no longer seeing elevated error rates when customers create app connections, and we can confirm that customers can create new app connections without issue.

This issue is now considered resolved, but feel free to reach out to our Support team if you have questions: https://zapier.com/app/get-help

Users are not able to create new app connections using OAuth flow

Status: Resolved This issue is now resolved.

Zaps that using Notion as a trigger should now be receiving all webhooks and triggering properly.

If you are still running into into issues, please reach out to Zapier Support: https://zapier.com/get-help

Zaps using notion triggers stopped triggering

Status: Resolved Our team has restored full functionality and verified system performance is stable. Since there's full functionality, the incident is considered closed.

Affected customers have been contacted but no further action is necessary.

If you have any other questions, please feel free to reach out to our support team at https://zapier.com/app/get-help Affected components
 <ul>
 <li>Polling Triggers (Operational)</li>
<li>Searches & Writes (Operational)</li>
 </ul>

Some app integrations experiencing delayed triggers sporadically

Status: Resolved This issue is now resolved, and the Task Usage Page should now be loading correctly for all users.

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

Task Usage Page Currently Unavailable

Status: Resolved Between approximately 10:00PM UTC on Feb 23 and 3:20 AM UTC on February 24, we saw errors being returned from the Transcribe cation in AI by Zapier. The team were able to identify and roll-back the change causing this issue and the issue should now be resolved.

If you run into any unexpected errors, please feel free to reach out to us at: https://zapier.com/app/get-help

AI by Zapier steps in Zaps with transcribe action running into an error

Status: Resolved On February 20, 2026, between 1:44 PM and 8:27 PM EST, an Airtable outage caused authentication errors and trigger delays for customers using Airtable integrations through Zapier. Affected Airtable authentications were marked as inactive, resulting in errors and delays for impacted automations. The Zapier platform remained fully operational throughout.

Airtable's services have since fully recovered. If you are still experiencing issues with your Airtable connections, please visit the Zapier Connections page to reconnect Airtable, and check your Zap History to replay any affected runs.

Airtable Authentication Expiring

Status: Resolved We are pleased to confirm that this incident has been resolved. All Airtable Zaps and connections are back to normal. Impacted customers have now received an email with a timeline of events, actions taken, and next steps (if any).

If you have any questions or need assistance, please reach out to our Support team at: https://zapier.com/app/get-help.

Upstream errors with Airtable authentications

Status: Resolved This issue has been resolved.
Between 14:42 and 18:00 UTC on February 12, some users were unable to view the Change History panel in the editor.
All systems are now operating normally. If you experienced issues during this time, please refresh your browser.
Need help? Contact Support: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Website (Operational)</li>
 </ul>

Change History Not Displaying

Status: Resolved This incident has been resolved as of 2026-02-12T15:38:00 UTC. Agents and Chatbots can now successfully add and sync table-based knowledge sources. If you encountered errors during the incident, please re-add and sync your knowledge sources.
Need help? Contact Support: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Chatbots (Operational)</li>
<li>Agents (Operational)</li>
 </ul>

AI Features Degraded — Chatbots & Agents

Status: Resolved Resolved — Facebook Custom Audiences Integration

The Facebook Custom Audiences integration issue has been fully resolved.

What happened: Our integration was calling a deprecated version of the Facebook Ads API (v22), which is no longer supported. This prevented some requests from completing successfully.

What we did:*We identified the issue and upgraded the integration to the latest supported API version (v23). We confirmed the update and rolled it out to all affected users. We also replayed failed runs to ensure they completed successfully.

Current status: All functionality has been restored and the integration is operating normally. All affected users are back to full service.

If you have any questions or experience any issues, please reach out to our support team: https://zapier.com/app/get-help

Facebook Custom Audiences integration retuns an deprecated API error

Status: Resolved Our Engineering teams have pushed out a fix for the issue, and we have confirmed this has resolved the issues with Copilot.

You may need to refresh the page if you're still seeing Copilot errors or if it's unresponsive while adding actions to a Zap.

If you have questions, please don't hesitate to reach out to our Support team at https://zapier.com/app/get-help

Copilot may show errors or become non-responsive when adding action to a Zap.

Status: Resolved We're happy to report that the LinkedIn team has successfully completed replaying the missed hooks for the New Lead Gen Form Response (Sponsored content) trigger that occurred during the incident window (Jan 27th, 8:21 UTC until Jan 29th, 01:32 UTC).

If you have any questions or need assistance, please reach out to our Support team at
https://zapier.com/app/get-help

LinkedIn Ads - All Triggers - Missing Webhooks

Status: Resolved We're happy to report that the issue related to failures associated with logging in to http://mcp.zapier.com/ has been resolved.

Functionality has been fully restored, and users can now login without error.

If you have any questions or need assistance, please reach out to our Support team at
https://zapier.com/app/get-help Affected components
 <ul>
 <li>MCP (Operational)</li>
 </ul>

OAuth Login Issues for New MCP Customers

Status: Resolved We are happy to report that the issue has been resolved and we are no longer seeing reports of issues from our customers. There's no action to take, and loading sample trigger data should now be working as expected.

Please let us know if you're still seeing issues or have questions!

Intermittent throttling errors when pulling a trigger sample

Status: Resolved The issue preventing some Email Parser triggers from firing has been resolved. Email processing is back to normal, and affected Zaps are running as expected.

We’re continuing to monitor the system and will take steps to prevent similar issues in the future. If you need help, please contact Support: https://support.zapier.com Affected components
 <ul>
 <li>Instant Triggers (Operational)</li>
 </ul>

Parser service disruption affecting mailbox access

Status: Resolved We're happy to report that the issue affecting the ability to create an Agent from a template has been resolved.

Earlier today, users encountered a generic error message ("Something went wrong while trying to use this template.") while attempting to create an Agent from an Agent template. Existing Agents were not affected.

Our engineering team has identified the issue and implemented a fix. Functionality has been fully restored, and users can now create Agents from templates as expected.

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

Agent templates is returning an error

Status: Resolved The incident affecting the broken redirection URL and affected links has been resolved. Some users were experiencing 404 errors when navigating from https://zapier.com/templates using the header links and dropdown menus.

The affected services have returned to normal operation, and we have not observed ongoing customer impact since resolution.

If you have any questions or need assistance, please don’t hesitate to reach out to our support team:
https://zapier.com/app/get-help

The Template page (https://zapier.com/app/templates) is redirecting, causing links on the page to return a 404

Status: Resolved The incident affecting LinkedIn actions in Zap runs has been resolved.

Between approximately 07:59 AM UTC and 11:55 AM UTC on January 16, 2026, some users experienced errors impacting Zap runs. These issues may have caused Zap runs to fail during this window.

As of 11:55 AM UTC, the affected services returned to normal operation. Zap runs that encountered errors during the incident window have been automatically replayed, and we have not observed ongoing customer impact since resolution.

If you have any questions or need assistance, please don’t hesitate to reach out to our support team:
https://zapier.com/app/get-help

LinkedIn apps returning "Requested version 20250101 is not active" error

Status: Resolved We are happy to report that the issue affecting the ability to create zaps from the actions panel in Forms has been resolved.

 Earlier today, some users encountered a generic error message (“Something went wrong”) when attempting to create new zaps from the Forms actions panel. Existing zaps and other methods for creating zaps were not affected.

 Our engineering team identified and corrected a broken link that was causing this error, which was related to a recent product rebrand. Functionality has been fully restored, and users can now create zaps from the Forms actions panel as expected.

 We apologize for any inconvenience this may have caused. Affected components
 <ul>
 <li>Forms (Operational)</li>
 </ul>

Creating new Zaps via Forms Actions panel seeing errors

Status: Resolved This issue is now resolved and all Tables functionality should return to normal. Any errored runs due to this incident were replayed.

Thank you for your patience, and if you are still running into any issue, please reach out to Support for assistance: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Tables (Operational)</li>
 </ul>

Increased timeout errors for Tables and associated workflows within a 3-minute window

Status: Resolved Our team has implemented a fix, and all app images are now displaying correctly in Zapier's App Directory.
If you're still seeing some broken images, please refresh your browser's cache and cookies, then load the page again.
Many thanks for your patience! The support team is always happy to help if you have any questions: zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help Affected components
 <ul>
 <li>Website (Operational)</li>
 </ul>

Some app images are not rendering correctly in Zapier's App Directory

Status: Resolved With HubSpot's confirmation that their service interruption has been resolved and our monitoring showing normal operations, this incident is now considered resolved. We have replayed all Hubspot data, which includes triggers and actions, that we have from the length of the incident.

Due to the HubSpot service interruption, some data may not have been sent to Zaps. We recommend checking HubSpot data against your Zaps to see if everything triggered as expected.

If you find that your automations did not trigger, we recommend reaching out to HubSpot support to see if this data can be resent to your Zaps.

HubSpot Support can be reached at https://help.hubspot.com/

Please do not hesitate to contact us with any further questions related to this incident.

Delayed triggers within Hubspot integration

Status: Resolved The issue causing deprecation errors in some Zapier Interfaces triggers has been fully resolved.

Between 00:00 UTC and 07:13 UTC on January 9, Zaps using older versions of the Zapier Interfaces CLI (primarily 1.8.22 and 1.8.27) experienced failures due to a deprecated API endpoint. While an initial fix was deployed, we observed continued errors during monitoring. Engineering implemented a final fix, and the issue has since subsided.

All impacted tasks have now been successfully replayed, and no data was lost. Systems are operating normally, and there is no ongoing impact.

If you continue to experience any issues, please contact our Support team: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Forms (Operational)</li>
 </ul>

Zap runs with the Zaper Interfaces app are returning a deprecation errors

Status: Resolved This issue has now been marked as resolved, and Zapier MCP with Claude should now be working properly without issue.

If you run in to any issues, please contact Support at:

https://zapier.com/app/get-help Affected components
 <ul>
 <li>MCP (Operational)</li>
 </ul>

Is Zapier down?

Zapier status is UP

Lastest published events

Copilots "Ask" mode is not working correctly

Errors related to Custom Actions and Code by Zapier steps

Intermittent agent execution failures

Zapier Services, Components and Regions

Recent Zapier events

Copilots "Ask" mode is not working correctly

Errors related to Custom Actions and Code by Zapier steps

Intermittent agent execution failures

Delayed or failed custom action requests

Functions not executing

Maintenance: Zapier Tables maintenance

Get your FREE account now,
5 monitors included!

Is Zapier down?

Zapier status is UP

Lastest published events

Copilots "Ask" mode is not working correctly

Errors related to Custom Actions and Code by Zapier steps

Intermittent agent execution failures

Zapier Services, Components and Regions

Recent Zapier events

Copilots "Ask" mode is not working correctly

Errors related to Custom Actions and Code by Zapier steps

Intermittent agent execution failures

Delayed or failed custom action requests

Functions not executing

Maintenance: Zapier Tables maintenance

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!