Skip to content
OutageDeck

Incident detail

Discord integration issues

Resolved incidentMinor

Timeline window

to

Get alerted the next time Zapier breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Zapier alerts work

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. 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. Resolved

    Discord requests made through Zapier's Proxy API — 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. If you need help, reach out at <https://zapier.com/app/get-help>.

Keep exploring

More from Zapier

Neighboring incidents on Zapier's timeline and the rest of their record on OutageDeck.

← Older incident

Connection errors affecting Salesforce Pardot Zaps

All Zapier incidentsZapier live status