Resolved after 2 hours 39 minutes, on October 29, 2026.
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.
Update timeline
- investigating Oct 29, 2026, 04: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.
- resolved Oct 29, 2026, 06: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 https://zapier.com/app/get-help.
- resolved Oct 29, 2026, 06: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 https://zapier.com/app/get-help.
Your product runs on more than Zapier
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services