Discord integration issues

What to do

• Check whether your product depends on Zapier. 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 40m it lasted.

  Anything that failed between 2026-10-29 16:13 UTC and 2026-10-29 18:53 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 2

1. investigatingOct 29, 2026, 4:13 PM UTC

   Some customers may experience failures when making Discord requests through SDK-based flows and Custom Actions. We’re investigating and may temporarily disable these requests to mitigate the issue; the Discord integration itself is not expected to be affected.

   provider

2. resolvedOct 29, 2026, 6:53 PM UTC

   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 .

   provider

Corrections

None so far.

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