https://cdn.discordapp.com/attachments/1503194050059046932/1503194050214494349/03_pencil_edits_alias_only.png?ex=6a02760d&is=6a01248d&hm=a2c8e3c584ba3e9ea15646d70f94a32fc25dd76280ddb6c2c0196f829d8e23bd& https://cdn.discordapp.com/attachments/1503194050059046932/1503194050562359296/01_successfully_connected_NO_form.png?ex=6a02760d&is=6a01248d&hm=856a4584c1f838fe4371ab3c29d9056f4c5f9aca90aaebe91ae801922385b7fe& https://cdn.discordapp.com/attachments/1503194050059046932/1503194050872741938/02_connected_accounts_no_edit_credentials.png?ex=6a02760d&is=6a01248d&hm=9f1f186e91562d39405f055bfbfa1c59f23e1565f8023c762c9078fa0ec0e778& https://cdn.discordapp.com/attachments/1503194050059046932/1503194051246293134/discordbot_bug_report.txt?ex=6a02760d&is=6a01248d&hm=3b4438db66baaf38582de7c87ecd751b8f772197594b83b423bd0618da7fc729&

Hi @Franddy, the images are really helpful in determining the service you are using and seems like it's For You. Currently, we have a configuration issue with our managed OAuth app which is casuing the 401s. Our team is actively trying to get our configs right and verified as soon as possible. I'll update you as soon as we fix the

discordbot

toolkit! Thanks for flagging this.

Thanks for confirming and for the transparency 🙏 Glad to know it's being worked on. Looking forward to the fix — in the meantime I'll proceed manually with Discord setup and hold off on the automation side until you ping me. If you need any additional logs, test scenarios, or my user_id to verify the fix on my workspace specifically, let me know. Cheers! — Franddy

Thanks for understanding, I'll keep you updated.

Update from my side, [date: 2026-05-16 ~22:46 UTC]: I ran another full test after your initial response. The behavior has changed slightly but the underlying bug persists: WHAT'S NEW (improvement): - OAuth flow now completes successfully - redirect_url is generated correctly - Connection callback fires and marks the connection as ACTIVE - COMPOSIO_MANAGE_CONNECTIONS list shows status: "active" WHAT'S STILL BROKEN: - The token stored after the OAuth flow does NOT authenticate against Discord's API - DISCORDBOT_TEST_AUTH returns: - auth_ok: false - status_code: 401 - GET /users/@me → 401 Unauthorized (code: 0) This is precisely the symptom DISCORDBOT_TEST_AUTH is designed to detect: a 401 on this specific endpoint means invalid token (not missing permissions, not wrong guild). DIAGNOSTIC DATA: - Test timestamp: 2026-05-16 ~22:46 UTC - connected_account_id: ca_Xll-qS17X6kH - auth_config_id: ac_Z8ME_yHrnsnz - log_id (failed test): log_PT4RXh29HxAu - previous request_id: 742dd180-0b30-497a-98d2-0bdfb2faff7d It seems something changed in the OAuth managed config since my initial report (flow now completes instead of hanging), but token exchange/storage is still producing invalid tokens. Happy to run additional tests or share more logs as you need them. Let me know if you need me to reproduce with verbose logging. Thanks! — Franddy (Helbreath Legacy)

Hi @Franddy, thanks for the details and really appreciate the patience. Quick update from our side: we've applied for a new OAuth app for Discord and it's currently under verification. The timeline on this is largely dependent on Discord's review pace, so it might take a little while before it's fully through. I'll keep you posted as soon as we hear back from them.

Thanks Andre, really appreciate the transparency on this 🙏 Good to know you're going the proper route with a new verified OAuth app — that's actually reassuring even if it takes longer. A patched fix would've been less reliable long-term. In the meantime I'll proceed with Discord setup manually and keep Facebook automation running through Composio (which works perfectly, by the way). When the new Discord OAuth gets verified and you ping me, I'll be ready to test and confirm from my side. If at any point you need a tester for the new app once it's through Discord's review, count me in — happy to validate the fix end-to-end on my workspace. Cheers! — Franddy

hi @Uday my apologies for the ping. Is there any feedback from the discord side are you just awaiting a response from their side? additionally, is there any workaround of making discordbot work with composio till then?

@Uday Hey noticed the discord bot is down. If there's no resolution, can you remove it from Composios managed config - its incredibly misleading.

Any update on this?

Hi there, Sorry this has dragged on. Honest status first: the verified Discord app is still in Discord's review queue, and that pace is on their side, so I don't have a firm date to share yet. You don't have to wait on that to get unblocked, though. discordbot authenticates every call as a Discord bot (

Authorization: Bot <token>

), and the managed connection relies on a Composio-owned bot token that Discord is currently rejecting, which is the 401 you're hitting. You can sidestep it entirely by connecting with your own Discord bot token: 1. In the Discord Developer Portal, open your application, go to Bot, Reset Token, and copy the new token. 2. Create a new discordbot auth config using custom credentials (not the managed/default one). 3. Paste the raw bot token only (no

Bot

prefix, no quotes or spaces), and set the Permission Integer. 4. Connect through that config and run

DISCORDBOT_TEST_AUTH

. That uses the exact

Bot <token>

auth discordbot expects, so it should clear the 401 independently of the managed app. If it still fails on the custom config, reply here with the new

auth_config_id

and

connected_account_id

and I'll dig into your specific connection. This response was generated automatically by Composio's AI support agent. If it doesn't fully resolve your issue, or you'd like to speak with a person, just reply here and a member of our team will take a look.