Skip to main content
Zapier

403 errors when trying to connect or reconnect to ActiveCampaign

Degraded Lasted 2h 31m · started · Zapier's page

Level
confirmed
Worst impact
Degraded
Regions
us
Down Index
23of 100

What to do

  • Check whether you use Zapier in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 2h 31m it lasted.

    Anything that failed between 2026-08-21 23:48 UTC and 2026-08-22 02:19 UTC may need a replay.
  • Subscribe to Zapier's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=zapier works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Zapier 3

  1. investigating

    We have reports that users who try to create new app connections or reconnect existing ones for ActiveCampaign receive a 403 error. This causes the connection to fail. Our Engineering team is looking into the issue and will follow up as soon as we learn more. If you're unable to log in, please open a case with our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help") so we can continue to keep you up-to-date.

    provider

  2. monitoring

    The issue with ActiveCampaign app connections returning a 403 error has been resolved. Authentication and integration are now functioning normally, and Zap runs using ActiveCampaign aren't impacted by this going forward. Our team is currently investigating which Zap runs were affected during the incident and will provide further updates as needed. Thank you for your patience and we appreciate you bearing with us as we worked through this. If you continue to experience any issues, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help").

    provider

  3. 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](https://zapier.com/app/get-help "https://zapier.com/app/get-help").

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-109a65540e

Is Zapier still down?

No, this incident was resolved 2026-08-22 02:19 UTC. For Zapier's live state, see https://down.guide/zapier.

How long did it last?

2h 31m, from 2026-08-21 23:48 UTC to 2026-08-22 02:19 UTC, by the times Zapier posted.

What was affected?

Zapier named in us.

What caused it?

Zapier hasn't published a root cause. If it does, it shows here.

Where does this come from?

Zapier's official status page, https://status.zapier.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.