# Zapier: Discord integration issues

- Provider: [Zapier](https://outages.live/zapier.md)
- Type: Incident
- State: Resolved
- Worst impact: Operational
- Started: 2026-10-29 16:13 UTC
- Resolved: 2026-10-29 18:53 UTC (lasted 2 h 40 min)
- Official update: https://status.zapier.com

## Updates from Zapier

### resolved, 2026-10-29 18:53 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 .

### investigating, 2026-10-29 16:13 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.