DISCORD n8n INTEGRATION: AUTOMATE DISCORD WITH N8N

The "Send a message" action is the cornerstone of Discord automation—it lets your bot post messages to any channel in your server programmatically. Whether you're sending notifications, alerts, welcome messages, or automated updates, this action handles it all.

Key parameters: Connection Type (Bot Token authentication), Credential for Discord Bot API (your stored bot credentials), Server (target server by ID), Send To (Channel or User), Channel (destination channel by ID), Message (text content with dynamic expressions support), Embeds (rich formatted messages), and Files (attachment support).

Use cases: Send automated welcome messages when users join via another integration, post daily summaries or reports from your database, notify your team channel when a new customer signs up, or alert moderators when specific conditions are met in your workflow.

This advanced action combines message sending with interactive response collection. Your bot sends a message and then pauses the workflow until a user responds, enabling approval workflows and interactive automations directly in Discord.

Key parameters: Connection Type (Bot Token), Server/Channel (specify location by ID), Message (prompt or question), Response Type (set to "Approval" for user approval/rejection), and Approval Options (define available response choices).

Use cases: Create approval workflows where managers approve requests via Discord, build interactive onboarding sequences that wait for user input, implement confirmation steps before executing sensitive operations, or gather feedback from team members before proceeding.

When to use it: Perfect for workflows requiring human-in-the-loop decisions. Instead of fully automated processes, you can pause for approval on expenses, content publishing, or access requests.

The "Get a message" action retrieves detailed information about a specific Discord message. This is essential for workflows that need to read message content, check reactions, or verify message existence before taking action.

Key parameters: Server (Discord server by ID), Channel (channel containing the message by ID), Message ID (unique identifier of the specific message), and Options (additional retrieval options).

Use cases: Verify a message exists before attempting to modify or delete it, extract message content for logging or analysis, check reaction counts on announcement posts, or build workflows that respond based on specific message content.

Need to retrieve multiple messages at once? This action fetches a batch of messages from a channel, enabling bulk operations, analysis, and monitoring workflows.

Key parameters: Server/Channel (identify target location by ID), Return All (toggle to fetch all messages), Limit (maximum number of messages to retrieve, default: 100), and Options (additional filtering or sorting parameters).

Use cases: Archive channel content to external storage or databases, analyze message patterns for moderation purposes, build search functionality across Discord messages, or monitor channel activity and generate reports.

The "Delete a message" action removes a specific message from a channel. Essential for moderation, cleanup, and maintaining channel organization.

Key parameters: Server (target server by ID, required), Channel (channel containing the message by ID, required), and Message ID (unique ID of the message to delete, required).

Use cases: Automatically delete messages containing prohibited content, clean up bot commands after execution, remove temporary notifications after a set time, or implement self-destructing messages for sensitive information.

This action adds an emoji reaction to a specific message. While simple, it's surprisingly powerful for acknowledgment systems, voting mechanisms, and automated feedback.

Key parameters: Server/Channel (location of target message by ID), Message ID (specific message to react to), and Emoji (emoji to add as reaction, supports standard and custom Discord emojis).

Use cases: Acknowledge receipt of support requests with a ✅, create voting systems where the bot adds reaction options, mark processed messages in a queue, or provide visual feedback on automated actions.

The "Create a channel" action lets you programmatically create new channels in your Discord server. Perfect for dynamic workspace organization or automated project setups.

Key parameters: Server (server where channel will be created, selectable from list), Name (name for the new channel, e.g., "project-alpha"), Type (Guild Text for text channels, Guild Voice for voice channels), and Options (additional settings like category, permissions, or topic).

Use cases: Automatically create project channels when new projects are added to your PM tool, generate temporary channels for events or meetings, build onboarding workflows that create dedicated support channels per customer, or create channels based on form submissions or CRM data.

Retrieve detailed information about a specific Discord channel, including its name, type, topic, permissions, and other metadata.

Key parameters: Server (server containing the channel by ID) and Channel (specific channel to retrieve information about by ID).

Use cases: Verify channel exists before sending messages, check channel permissions before attempting operations, log channel metadata for auditing purposes, or build conditional workflows based on channel properties.

Fetch a list of channels from a Discord server, useful for auditing, reporting, or building channel selection interfaces.

Key parameters: Server (target server to list channels from by ID), Return All (toggle to fetch all channels), Limit (maximum number of channels to return, default: 100), and Options (filter or sort options).

Use cases: Generate server structure reports, audit channel organization, build dynamic channel selectors for other workflows, or monitor for unauthorized channel creation.

Modify an existing channel's properties, including its name, topic, permissions, or category placement.

Key parameters: Server/Channel (identify channel to update by ID), Name (new name for the channel), and Options (additional properties to update such as topic, slowmode, NSFW flag, etc.).

Use cases: Automatically rename channels based on project status, update channel topics with live information (like support queue status), archive channels by moving to an archive category, or implement channel naming conventions automatically.

Remove a channel entirely from your Discord server. Use with caution—this action is irreversible.

Key parameters: Server (server containing the channel by ID, required) and Channel (channel to delete by ID, required).

Use cases: Clean up temporary event channels after events end, remove project channels when projects are completed, implement automated channel lifecycle management, or delete test channels created during development.

Retrieve a list of members from your Discord server with their details, enabling bulk member operations and reporting.

Key parameters: Server (server to list members from by ID), Return All (toggle to fetch all members), Limit (maximum number of members to return, default: 100), After (member ID to start listing after for pagination), and Options (additional filtering parameters).

Use cases: Export member lists for analysis or backup, build member directories synced with external tools, audit member counts and activity, or generate reports on community growth.

Assign a role to a specific member in your Discord server. Essential for automated onboarding, reward systems, and access management.

Key parameters: Server (target server by ID, required), User (member to assign role to, selectable from list), and Role (role(s) to add, accepts dynamic expressions for role IDs).

Use cases: Automatically assign "Customer" role when users make a purchase, grant access roles based on form submissions or verifications, implement gamification with automatic role upgrades, or sync roles with external membership systems like your HubSpot CRM integration.

Remove a role from a specific member, enabling automated access revocation and role management.

Key parameters: Server (target server containing the member by ID), User (member to remove role from, selectable from list), and Role (role(s) to remove, accepts expressions for dynamic role IDs).

Use cases: Automatically remove trial access roles when trials expire, revoke permissions when subscriptions are cancelled, implement temporary roles that expire after set periods, or sync role removals with external CRM or membership platforms.

When to use it: Combine with "Add a role to a member" to build complete role lifecycle management—automatically granting and revoking access based on external events. Explore more workflow creation possibilities for advanced use cases.