Zapier did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-11-04 20:28 UTC. This page shows the end time when Zapier marks it resolved.

How do I get alerts for Zapier?

Subscribe to the Zapier live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Zapier. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

ZapierIncident ·

Chat with Sales temporarily unavailable

Q: What happened?

Zapier reported "Chat with Sales temporarily unavailable" on its status page at 2026-11-04 20:28 UTC. Zapier reports that the Chat with Sales feature on zapier.com does not work for some visitors. Zapier is investigating the problem. Zapier states that users can contact the Support team for help until the problem is fixed.

NoticeOfficial update

Zapier reports that the Chat with Sales feature on zapier.com does not work for some visitors. Zapier is investigating the problem. Zapier states that users can contact the Support team for help until the problem is fixed.

State

Investigating

Started

Ongoing for

1 h 35 min

Worst impact

Notice

Timeline

1 update

20:2820:5221:1621:3922:03

NoticeUpdate postedTimes in UTC

Investigating

1 h 35 min 100%

Updates

Times in UTC

As posted by Zapier

Investigating

Some visitors to [zapier.com](http://zapier.com) may be unable to start a chat with our Sales team right now. If you need help in the meantime, you can reach our Support team at . We're looking into this and will share an update as soon as we know more.

Zapier in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 51 min

This incident

44% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 days

median 2 h 51 min

90 days agoToday

Other Zapier incidents

All incidents

Zapier·Delayed or failed template recommendations and template setup

Zapier template recommendations and template setup did not work for some users. The problem started at 21:03 UTC and lasted 37 minutes. Zapier reports that the issue is resolved.

Resolved

Zapier·"Chat with Sales" page not loading

We have tested the page post-fix and the issue is resolved. Users visiting the "Chat with Sales" page ( ) should now be able to see the chat session. This incident is now considered resolved. If you don't see the chat, we recommend clearing your browser cache and cookies, then trying the page again. If you continue to have issues with the page, reach out to our support team at [zapier.com/app/get-help](http://zapier.com/app/get-help).

Resolved

Zapier·Discord integration issues

Discord requests made through [Zapier's Proxy API](https://docs.zapier.com/proxy-api/overview) — where Zapier adds the credentials for a connected Discord account on behalf of your code or an agent (for example via the Zapier SDK, Code by Zapier, Custom Actions, MCP code actions, or Sidekick) — have been disabled and will no longer be available. Affected requests return a `401 Unauthorized` error. This does not affect Zapier's native Discord integration — standard Discord triggers and actions continue to work as normal. Code steps that call Discord with a token you supply yourself (rather than a connected Discord account) are also unaffected. If you were making direct Discord requests this way, you can switch to Zapier's [native Discord integration](https://zapier.com/apps/discord/integrations). If you need help, reach out at .

Resolved

Zapier·Connection errors affecting Salesforce Pardot Zaps

This issue originated in an upstream incident with Salesforce's Pardot service, which caused some Pardot connections to fail when refreshing authentication. Salesforce has remediated their side, but affected connections need to be reconnected. We've deployed a fix on our side so that affected connections now show as expired. To restore your connection, reconnect your Salesforce Pardot account in Zapier. Some Zaps may have been delayed or held, and we're checking that they resume after reconnecting. If your Zaps are still failing after reconnecting, or you need help, please contact our support team: [ https://zapier.com/app/get-help](https://zapier.com/app/get-help " https://zapier.com/app/get-help")

Resolved

Zapier·Security updates in progress for third-party software components

We have not identified any customer impact or evidence of exploitation. We have completed the priority security updates and mitigations, and are closing this incident. Remaining lower-risk updates, including updates managed by our providers, will continue as follow-up work. No action is needed on your part.

Resolved

Follow Zapier

Your coding agent knows when Zapier is down, and tells you when a failure is theirs, not yours. You can also get Zapier incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "zapier" and tell me if Zapier has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=zapier

Slack

/feed subscribe https://outages.cc/feed.xml?providers=zapier

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane