No impact incident

Zapier: Discord integration issues

Current status of Zapier: Operational — live Zapier status

Timeline

1. Oct 29, 2026, 16:13 UTC
   investigating
   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.
2. Oct 29, 2026, 18:53 UTC
   resolved
   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 .

Updates as published by Zapier.