Status: Resolved The issue is now considered resolved, with both Facebook and Microsoft single sign-on working as expected.

If you find yourself still unable to log in, please reach out to our Support team at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help

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

Logging into Zapier using Facebook or Microsoft SSO shown a blank page after authentication.

Status: Resolved This has been fully resolved. If you still face this issue, please reach out to our support team via the Get help and support with Zapie "Get help and support with Zapie": https://help.zapier.com/hc/en-us/articles/8496213764877-Get-help-and-support-with-Zapierr channels Affected components
 <ul>
 <li>Instant Triggers (Operational)</li>
<li>Polling Triggers (Operational)</li>
 </ul>

Azure DevOps connections failing: expired OAuth client secret (AADSTS7000222)

Status: Resolved The issue intermittently affecting Agent runs and Zap runs using AI by Zapier has been resolved. The confirmed impact window goes from September 18, 2026 at 2:00am UTC to today, September 21, at 15:00 UTC. 

Our team continues to work with our service provider to prevent this issue in the future, implement better safeguards, and consolidate self-healing capabilities.

Some Agent runs from previous days (September 18 to September 20) could not be replayed to avoid duplicate agent executions.

For Agents, if you want to replay affected runs, go to your Agents dashboard: https://agents.zapier.com/bots, open the All Activity: https://agents.zapier.com/activity tab to view recent runs, and review the agent runs during the incident window. You can replay any runs that need to be reprocessed by prompting the agent in the chat to retry.

For Zap runs using AI by Zapier, no action needed. Our team has successfully replayed all affected AI by Zapier runs.

Many thanks for your patience while we worked through this. If you gave any questions or need help, reach out to our support team at: zapier.com/get-help. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Agent runs (agents.zapier.com) intermittently experiencing 429 errors

Status: Resolved We have implemented a fix regarding Zap history runs not showing, so they should be available in your Zap history page now.

If you have questions or need help, please contact our Support team at: zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help. Affected components
 <ul>
 <li>Zap History (Operational)</li>
 </ul>

Zap History not displaying Zap runs

Status: Resolved The issue causing some Zap workflows to not trigger from webhooks or fail on action steps between approximately 8:15–9:50 AM ET has been resolved.

If you're still seeing issues with a Zap that should have run during this window, contact Support: zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help Affected components
 <ul>
 <li>Instant Triggers (Operational)</li>
<li>Searches & Writes (Operational)</li>
 </ul>

Webhook Triggers and Zap Actions - Service Disruption

Status: Resolved Freshservice webhook triggers are now delivering to Zapier again following a fix deployed by Freshservice. We’ve confirmed incoming webhook activity has resumed and are continuing to monitor volumes.

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

Thank you for your patience.

Freshservice - Webhook delivery disruption

Status: Resolved The issue affecting Tables, Chatbots, and Forms has been resolved as of approximately 15:00 UTC.

Some users were unable to load existing Tables, Chatbots, or Forms and were redirected to a creation page instead.

All affected surfaces — Tables, Forms, Chatbots, and folder/subfolder creation — have been verified and are working normally.

No data loss occurred, and Zap runs were not affected.

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

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

Tables, Chatbots, and Forms not loading for some customers

Status: Resolved Instant trigger processing has returned to normal. We have successfully replayed the affected triggers and continue not to see any impacted Zap runs, so the incident is now resolved.



If you have any questions, please reach out to our support team: [https://zapier.com/app/get-help](https://zapier.com/app/get-help) Affected components
 <ul>
 <li>Instant Triggers (Operational)</li>
 </ul>

Intermittent instant trigger failures

Status: Resolved Salesforce connections have recovered and authentication errors have returned toward normal levels. Customers should now be able to use their Salesforce integrations normally. We will continue to monitor recovery.

Salesforce integration - trigger and connection disruptions

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: 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.

Is Zapier down?

Zapier status is UP

Lastest published events

Logging into Zapier using Facebook or Microsoft SSO shown a blank page after authentication.

Azure DevOps connections failing: expired OAuth client secret (AADSTS7000222)

Agent runs (agents.zapier.com) intermittently experiencing 429 errors

Zapier Services, Components and Regions

Recent Zapier events

Logging into Zapier using Facebook or Microsoft SSO shown a blank page after authentication.

Azure DevOps connections failing: expired OAuth client secret (AADSTS7000222)

Agent runs (agents.zapier.com) intermittently experiencing 429 errors

Zap History not displaying Zap runs

Webhook Triggers and Zap Actions - Service Disruption

Freshservice - Webhook delivery disruption