Run community campaigns in Discord without manual work. Send posts, start direct messages, wait for replies, and change roles automatically. Ideal for marketing and community teams that manage events, onboarding, and member engagement at scale.

An MCP server trigger exposes a set of Discord tools your agent or chat UI can call on demand. The workflow uses a Discord bot to list servers, then fetch channels and members for a selected server. It can send a message to a channel and wait for a human reply, or DM a user and pause until they answer. It also adds or removes roles programmatically. With these actions, teams can run surveys, qualify members, and grant access based on responses, all from one place.

You will need a Discord bot with permissions to view channels, read and send messages, and manage roles. Map the server, channel, user, and role IDs or let your MCP client pass them at run time. Expect faster outreach and fewer repetitive steps. A role clean up that takes an hour can drop to minutes. Great for event RSVPs, gated channel access after a quiz, and follow ups after a campaign.

• MCP server trigger exposes Discord actions to an agent or chat UI
• Send a message to any channel by server and channel ID
• Post to a channel and wait for a human reply to capture answers
• Send a direct message to a user and pause until they respond
• Programmatically add or remove roles for selected members
• List all servers the bot is in using a simple API call
• Fetch all channels and members for a chosen server for precise targeting
• Single Discord bot credential reused across nodes for easy setup

• Reduce manual role updates from 60 minutes to 5 minutes by automating add and remove tasks
• Automate up to 80 percent of repetitive member outreach with channel posts and DMs that wait for replies
• Improve targeting accuracy by using live server, channel, and member lists for the correct audience
• Handle multiple servers from one bot so community managers can scale outreach without extra staff
• Connect campaign actions to real member responses to increase engagement and conversion

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Discord. See the Tools Required section above for links to create accounts with these services.
3. In the Discord Developer Portal, create an application and add a bot. Invite the bot to your server with permissions to view channels, read messages, send messages, and manage roles.
4. Copy the bot token from the Developer Portal and keep it secure.
5. In n8n, open Credentials. Create a new Discord Bot credential. Paste the bot token and give the credential a clear name such as Discord Bot Main.
6. Open each Discord node. In the Credential to connect with field, select your Discord Bot credential or click Create new credential and follow the on screen steps.
7. Get your target server ID, channel ID, user ID, and role ID from Discord by enabling Developer Mode in Discord settings and using Copy ID on each item.
8. Run the Get Discord Server IDs node to confirm the bot can list your servers. Use the correct server ID in other nodes or let your MCP client pass it at run time.
9. Test messaging: execute Send to Channel and Wait for Reply in a test channel. Post a reply in Discord and confirm the node captures the response.
10. Test roles: use Add Role To Member with a test role. If it fails, move the bot role higher than the target role and make sure Manage Roles is granted.
11. If member or channel lists are empty, enable Server Members Intent and Message Content Intent for your bot in the Developer Portal and try again.