# Discord integration issues

- Provider: [Zapier](https://down.guide/zapier)
- Level: confirmed
- Impact: Degraded
- lasted 2h 40m
- started 2026-10-29 16:13 UTC
- id: DWN-44ab69d22a
- Official page: https://status.zapier.com/incidents/01M6470SKX5YZT3H9MKWXE244Z

## Updates from Zapier
### 2026-10-29 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.

### 2026-10-29 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 .

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).