Status: Resolved The issue with ActiveCampaign app connections and runs returning a 403 error has been fully resolved. Authentication and integration are functioning normally again.

Impacted runs during the incident period have been replayed successfully.

If you're experiencing any issues, please reach out to our Support team through this link: https://zapier.com/app/get-help.

403 errors when trying to connect or reconnect to ActiveCampaign

Status: Investigating We are continuing to investigate an issue affecting Salesforce integrations in Zapier. Some Salesforce connections were invalidated and may show as expired or disconnected in My Apps.

How to tell if you’re affected
• Go to My Apps: https://zapier.com/app/connections
• If your Salesforce connection shows as expired or disconnected, you’re affected
• Zaps that use that Salesforce connection as a trigger (especially polling triggers) may stop firing while the connection is expired
• You may also see held Zap runs or trigger authentication failures in Zap History

What to do
Reconnect the affected Salesforce connection from My Apps. Use a Salesforce user that has permission to authorize the connection in your org.

Once reconnected, polling triggers should resume on their normal schedule. Held or missed runs should begin processing again after the connection is healthy.

Other impact
Zap steps that do not use the affected Salesforce connection, and workflows outside Salesforce, are not broadly affected based on what we know so far.

What we’re doing
Re-authentication has restored service for customers who have the required Salesforce permissions. We have not deployed a platform-wide fix yet. We are investigating why these connections were invalidated and coordinating with Salesforce. We will provide another update within 60 minutes.

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

Salesforce integration - trigger and connection disruptions

Status: Resolved Errors related to Pipedrive invalid IDs are resolved. If you have any further questions, please reach out to us: https://zapier.com/app/get-help

Errors related to Pipedrive invalid IDs

Status: Resolved After monitoring traffic, we're seeing forms respond as expected. We now consider the issue resolved.

Thank you for your patience as we worked to resolve the issue. Affected components
 <ul>
 <li>Website (Operational)</li>
 </ul>

Sales Contact forms are not loading

Status: Resolved The issue affecting Zapier Functions has been resolved. Functions are now operating normally.

During this incident, users were unable to create, edit, or run Functions. No data loss occurred. Zaps and other Zapier services were not affected during this time.

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

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

Zapier Functions temporarily unavailable

Status: Resolved This incident has been resolved. Submissions to our Contact Sales, webinar/event registration, ZapConnect registration, and AI Leaders Lab forms are working normally again.

The issue was caused by our third-party form provider’s daily API limit being exhausted by internal Zapier traffic, which prevented these marketing-site forms from loading and submitting. The upstream limit has been raised, the internal traffic source has been stopped, and form submissions have been confirmed stable.

Thanks again for your patience while we were working on resolving that, and 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

Contact Sales forms is down

Status: Resolved We have successfully resolved the Salesforce connection issues that affected some of our customers earlier today.

What Happened

A recent update to our Salesforce integration caused authentication failures for users who were automatically migrated to the new version. Customers attempting to connect or reconnect their Salesforce accounts received an error message.

What We Did

Our team quickly identified the root cause, stopped further migrations, and rolled back all affected users to a previous working version. We then systematically reactivated all affected Salesforce connections and replayed any impacted Zap runs to ensure no data was lost.

Resolution

All Salesforce connections have been restored and are now working normally. Your Zaps should resume processing automatically. If you experienced any issues earlier today, your connections are now active and ready to use.

Thank You

We sincerely apologize for this disruption and appreciate your patience as we worked to resolve this issue. If you have any questions or continue to experience problems, please contact our support team at https://zapier.com/app/get-help.

Thank you for your continued trust in Zapier.

Salesforce Integration Issue

Status: Resolved This issue affecting the Close CRM integration has been resolved.

Customers should now be able to connect or reconnect their Close account in Zapier normally. We have also replayed impacted delayed/held Zap runs that were paused during the incident.

If you’re still seeing errors connecting or reconnecting Close, please retry and contact Zapier Support at: https://zapier.com/app/get-help.

Close CRM integration: authentication issues

Status: Resolved We previously reported quota-exceeded errors affecting a subset of Zap workflows using Google Drive, Google Sheets, Google Docs, Google Slides, and Gmail actions.

The underlying issue has been fixed. Affected Zap runs have been replayed, and workflows that were paused due to elevated errors have been restored.

No further action is needed on your end. If a Zap run still shows as failed, you can replay it from your Zap history, or contact Support at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help.

Quota exceeded errors on a subset of Zap runs using Google apps integrations

Status: Resolved The rollback was successful, and the Google Drive quota errors have been resolved. All Google Drive actions are back to normal. Errored runs have been replayed automatically.

Many thanks for your patience while we worked through this. If you have any questions, please reach out to our Support team at zapier.com/get-help: http://zapier.com/get-help.

Elevated errors for Google Drive app integration

Status: Resolved We've resolved an issue that could cause new BambooHR connections or reconnection attempts to fail with an unclear authentication error and status code 403. The issue stemmed from one of the endpoints we used to verify BambooHR connections becoming unreliable.

We've updated our connection check to use a more reliable endpoint and corrected the error messaging so any future authentication issues will show a clear, actionable reason.

What you need to do:


• If your BambooHR Zaps have continued running normally throughout, no action is required.
• If you were previously unable to create a new BambooHR connection or reconnect an existing one "reconnect an existing one": https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK29AAFDNP7AS4PQ1NNM6, please try again, this should now succeed.
• If you're unsure whether your connection was affected, we recommend testing "testing": https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK296C9MCSX29305AKVZY your BambooHR connection "BambooHR connection": https://zapier.com/app/assets/connections?app=BambooHRCLIAPI from your account settings to confirm.


We apologize for any disruption this caused and thank you for your patience. Affected components
 <ul>
 <li>Zap Editor (Operational)</li>
 </ul>

BambooHR: Testing/creating connections fail with status code 403

Status: Resolved Earlier today, some Translate by Zapier requests failed with 403 “User Rate Limit Exceeded” errors due to a Google Integrations Production Google Cloud billing configuration issue.

This has been resolved and we’re seeing successful translations again with no ongoing errors.

If you had Zap runs fail during the incident window, you may need to replay those runs to complete processing.

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

Thank you for your patience.

Translate by Zapier – Elevated Error Rate

Status: Complete The scheduled maintenance has been completed successfully. All services are operating normally. Affected components
 <ul>
 <li>Polling Triggers (Operational)</li>
 </ul>

Maintenance: Scheduled Maintenance: Infrastructure Upgrade

Status: Resolved This incident has been resolved.

Between approximately 8:00 AM and 9:15 AM CDT (13:00–14:15 UTC), customers may have experienced errors or degraded functionality across multiple Zapier products, including: AI by Zapier, Agents, Chatbots, Forms, Interfaces, Tables, account management, and Zap runs and related automation processing.

The underlying issue has been fixed, systems are operating normally, and affected Zap runs and webhook events have been replayed.

If you’re still seeing issues, try refreshing the page, logging out and back in, or retrying any failed actions or workflow runs.

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.

Elevated authentication errors (401s) impacting multiple products

Status: Resolved The issue impacting AI by Zapier has been mitigated and systems are back to normal.
Impact window: Approximately 19:00–22:20 UTC on July 11.
We have automatically replayed the affected runs to recover previously failed executions.
If you have any remaining questions or are still seeing issues, please contact support at https://zapier.com/get-help.

AI by Zapier

Status: Resolved Issues related to Airtable errors are resolved. Any missed triggers and/or actions are replayed.

If you have any questions, you can always reach out to our support team here: https://zapier.com/app/get-help

Increased 4XX errors from Airtable

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.

Is Zapier down?

Zapier status is UP

Lastest published events

403 errors when trying to connect or reconnect to ActiveCampaign

Salesforce integration - trigger and connection disruptions

Errors related to Pipedrive invalid IDs

Zapier Services, Components and Regions

Recent Zapier events

403 errors when trying to connect or reconnect to ActiveCampaign

Salesforce integration - trigger and connection disruptions

Errors related to Pipedrive invalid IDs

Sales Contact forms are not loading

Zapier Functions temporarily unavailable

Contact Sales forms is down