Discord integration issues
none- Started
- Oct 29, 12:13 PM EDT
- Resolved
- Oct 29, 2:53 PM EDT
- Duration
- 2h 40m
Zapier's updates (2)
- investigating · Oct 29, 12:13 PM EDT
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.
- resolved · Oct 29, 2:53 PM EDT
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 <https://zapier.com/app/get-help>.
What our checks recorded
We checked Zapier 32 times from Zapier's start time to its resolution, once every five minutes. Every one of them reached Zapier's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 183 ms, against 166 ms over the 24 hours before. Zapier posted the incident at Oct 29, 12:13 PM EDT.
Updates are Zapier's own words from its status page (status: resolved); we never add an inferred cause.