Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I'm experiencing persistent issues with the "New User Added" trigger for Discord. Specifically, the Discord connection in my Zap keeps expiring or disconnecting shortly after setup.

I came across the following community post:
“Trouble with Discord connections expiring in Zapier”
→ https://community.zapier.com/rate-limits-125/trouble-with-discord-connections-expiring-in-zapier-46794

My issue seems similar, and I'm wondering if it's part of the same underlying problem.

Here is how I'm using the integration:

  • I’m only using the trigger to detect when a new user joins a specific Discord server.

  • I’m not sending any messages or performing actions back to Discord.

  • I'm using the official Discord app in Zapier, not custom webhooks or bots.

  • I have reconnected the Discord account several times, but the connection consistently drops within a short time.

My Questions:

  1. Is a bot necessary for this trigger to function even if no actions are sent back to Discord?

  2. What exact permissions are required on the Discord side to maintain a stable connection for the "New User Added" trigger?

  3. Is this part of the known issue reported in the thread above, and if so, is there any update or workaround available?

I’d really appreciate a technically accurate and up-to-date answer, as this affects a critical part of our automation setup.

Thank you!

Hello ​@Pento ,

I believe a bot is required, even for passive triggers like detecting new users joining a server. Most likely this is for security reasons. You also need at least the View Channels, Read Member List for the permission. No need for Send Messages unless you’re doing actions back.

Actually, many users experience connections expiring shortly after setup and I also cannot see any published update on the official fix about this issue. One workaround is to set up a custom bot through the Discord Developer Potal and host it on a plaform like Replit, Railway, or a cloud function. Listen for an event using a bot framework and send data to a Zapier webhook URL. Downside is this maybe a more technical set up. The other option is to use another third-party Discord integration platform.

You might also want to contact Zapier support regarding this issue.

Hey ​@Pento 

Jumping in to lend hand!

Yes, a bot is required for the "New User Added" trigger to work in Discord, even if you’re not sending actions back to Discord. This is because Discord’s API only provides these events through a bot connection, not just standard OAuth.

For a stable connection, make sure the Zapier bot has these permissions:
- Manage Webhooks (essential for all Discord triggers in Zapier)
- View Channels (to see new members)
- Read Message History (for monitoring events)
- You’ll also need to be a server owner or have the Administrator role

If your connection keeps dropping, it’s often due to missing permissions or the bot’s role not being high enough in your server’s role hierarchy. Try these steps:
1. Check that the Zapier bot’s role is above the roles it needs to interact with.
2. Double-check that Manage Webhooks and the necessary channel permissions are enabled for the bot.
3. To reconnect, disconnect the current Discord connection in Zapier, remove the Zapier bot from your server, wait a few minutes, then add a fresh connection with admin permissions.

It’s normal for the Zapier bot to appear offline in your server—this doesn’t affect its ability to trigger Zaps.

If you’re still running into issues after these steps, please reach out to Zapier Support using the Contact Form so the team can take a closer look.

Hope this helps clarify things!

 
Terms & Conditions