Discord Trigger Node Fixed For 2025 TS

:tada: n8n-nodes-discord-trigger-new - Major Update v0.10.11 (2025 Compatible)

Hi everyone!

I’m excited to announce that n8n-nodes-discord-trigger-new has been completely updated and is now fully compatible
with 2025 n8n versions!

:wrench: What’s Been Fixed

Over the past few days, I’ve been working hard to modernize and stabilize this community node. Here are the major
improvements:

Core Fixes & Stability

  • :white_check_mark: Cross-platform support - Now works seamlessly on Windows, Linux, and macOS
  • :white_check_mark: IPC handling improvements - Fixed timeout issues and enhanced connection management
  • :white_check_mark: Client cleanup on restart - Proper cleanup handlers for process termination
  • :white_check_mark: Multi-bot support - Multiple credentials across multiple workflows now work correctly
  • :white_check_mark: Unix/Linux compatibility - Fixed bot startup logic for Unix systems

New Features Added

  • :new_button: Message Debounce & Cooldown - Control how frequently triggers fire to prevent spam
  • :new_button: Channel Status Actions - Lock, unlock, archive, and unarchive channels
  • :new_button: Category Filtering - Filter channels by Discord categories
  • :new_button: Disabled Channels Management - Manage which channels to ignore
  • :new_button: Custom Button Labels - Customize confirmation message button text
  • :new_button: Enhanced Guild Member Updates - Better tracking of role changes and member updates

:package: Installation

npm install n8n-nodes-discord-trigger-new

Or install via n8n UI: Settings → Community Nodes → Install

Package name: n8n-nodes-discord-trigger-new

:rocket: Current Version: v0.10.11

:clipboard: Full Changelog (Recent Updates)

  • v0.10.11: Enhanced support command handling
  • v0.10.10: Global cleanup handlers for process termination
  • v0.10.9: Fixed debounce/cooldown settings organization
  • v0.10.8: Added message debounce and cooldown features
  • v0.10.1: Channel status actions (lock/unlock/archive)
  • v0.10.0: Category filtering and disabled channels
  • v0.8.3: Unix/Linux bot startup fixes
  • v0.8.2: Cross-platform IPC configuration

:test_tube: Testing

Tested and confirmed working on:

  • n8n version 1.75.2 and above
  • Windows 10/11
  • Linux (Ubuntu/Debian)
  • macOS

:link: Resources

:light_bulb: How to Use

  1. Set up a Discord bot via Discord Developer Portal
  2. Enable Message Content Intent in Privileged Gateway Intents
  3. Install the community node
  4. Configure credentials (Bot Token, Client ID, n8n API Key, Base URL)
  5. Start building your Discord workflows!

:folded_hands: Feedback Welcome

Please test it out and let me know if you encounter any issues. I’ve fixed all the major bugs that were preventing
it from working with modern n8n versions, but there’s always room for improvement!

If you find this node useful, please consider giving it a :star: on GitHub!

Happy automating! :robot:

Hi, I downloaded it but I can’t make it work. it says “Already logging in - close and reopen this node”. That’s what I did but it still does not work, can you help me pls ?

it’s working now. However it seems that the trigger does not work when it’s a message from a bot, is this normal ?

How did you configure the message trigger?

There is a example. I did regex .* because i need to trace all messages. If you need mention or like with starts you can do like that.

Also config;

it’s perfect, now everything is working ! Your tool is amazing !! Thanks a lot for you work !

:tada: Discord Trigger Node v0.11.0 - Major Voice Update!

Hey n8n community!

Excited to share a major update for the Discord Trigger node. You can now record and process voice from Discord voice
channels in your workflows!

:studio_microphone: What’s New

New Discord Voice Trigger Node

  • Record voice conversations from Discord channels
  • Multiple audio formats (OGG, PCM, WebM)
  • Voice activity detection (trigger when someone speaks)
  • Join/leave voice channel events
  • Multi-speaker recording support

AI-Ready

  • Built-in transcription support (Whisper, Google Speech-to-Text)
  • Direct integration with ChatGPT workflows
  • Base64 audio output for easy processing

Smart Filtering

  • Filter by user roles
  • Ignore bots option
  • Specific user ID filtering

:wrench: Technical Improvements

Fixed Duplicate Bot Issues

  • New global mutex system prevents duplicate bot instances
  • No more duplicate event listeners on restart
  • Works on Windows, Linux, and macOS
  • Better memory management and cleanup

:light_bulb: Use Cases

  • Record Discord meetings automatically
  • Create voice-activated workflows
  • Build voice bots with ChatGPT
  • Transcribe conversations to text
  • Monitor voice channel activity

:package: Installation

npm install n8n-nodes-discord-trigger-new@latest

:rocket: Example Workflow

Discord Voice Trigger → Audio Recording → Transcription → ChatGPT → Discord Reply

:clipboard: Requirements

  • n8n v1.75.2+
  • Discord bot with voice permissions
  • Node.js 18.10+

:folded_hands: Thanks

This update was built based on community feedback. Special thanks to everyone who requested voice features!


Note: Your Discord bot needs voice channel permissions to use voice features. External API keys may be required for
transcription services.

Questions? Comments? Let me know below!

Happy automating! :rocket:

This node looks great. I am working on getting the voice transcription to work. I’ve given the node itself all the info it needs for whisper as it is an option, but that does not seem to provide a transcription. I am having the bot save an ogg file, which seems to work wheneve rI speak but the files it is making are empty and my voice is going correctly through the chat as others can hear me. So using the file on a following code node like in the instructions does not seem to work either.


Do you have a solution to this problem?
I’ve encountered this issue in both version 0.8 and this version. I still can’t find a solution to this problem.

Hey,
I am trying hard to setup the trigger but I can’t get rid of the error
”already logging in …”

I think I am ok with the 3 first setup steps

  1. Set up a Discord bot via Discord Developer Portal :white_check_mark:

  2. Enable Message Content Intent in Privileged Gateway Intents :white_check_mark:

  3. Install the community node :white_check_mark:

  4. Configure credentials (Bot Token, Client ID, n8n API Key, Base URL) :exclamation_question_mark:

    1. Bot Token :white_check_mark:
    2. Client ID :white_check_mark:
    3. n8n api Key :white_check_mark:
    4. Base URL :exclamation_question_mark:

I am running n8n on a local machine, in a Docker Container. So bacisaly, my api server looks like

http://localhost:5678/api/v1

Is it possible to run this node on a local server ?
Thank you for you help. The functions look so appetizing

PS : I am not an IT pro, and my understanding is quite slow.

Hy Kevin, I’m having the same problem. How did you make it work ?

it’s about encoding i did email to discord i am still searching they are not allowing to get voice over bots

can you send me detailed log’s please hide your token or sensetive info like ******

as i reply to @Danai_Limparserd i asked discord how we can get clear audio from bot’s because i didn’t understand their voice documention and not really documented

Subject: Issue with Server/Channel List not loading and Manual ID entry failing

Message:

Hi, thank you for your response. Let me clarify my situation to ensure we are on the same page.

My goal is simple: I want to trigger the workflow whenever an image (attachment) is uploaded to a specific Discord channel.

However, I am facing a persistent issue with the node configuration:

1. UI Issue: Even though my Bot Token is valid and I have enabled all Privileged Gateway Intents (Presence, Server Members, Message Content) in the Discord Developer Portal, the “Server Names or IDs” and “Listen to Channels” dropdown lists remain empty/blank.

2. Manual Entry Failed: I tried to bypass the UI issue by entering the Server ID and Channel ID manually using Expressions (I tried both String format {{ “123…” }} and Array format {{ [“123…”] }}), but the node throws a validation error saying the value is not supported or “credentials missing”.

Could you please advise on the correct syntax to manually input the Server/Channel IDs if the list doesn’t load? Or is there a known compatibility issue with the latest n8n Docker image?

Thanks for your help!

Thank you for your very quick reply,
Sorry for such a basic question, but whare can I find this log file?

Hi Swenenzy,
I didn’t find interesting log. They must be somewhere out of my knowledge.
However, the only log that says something when the error occurs is n8n log displayed in docker container details. It says

“Cannot use ‘in’ operator to search for ‘description’ in undefined”

By th way, I should clarify the situation it happens:

I can set my credentials, when I test them it returns “Connection tested successfully “. Then I come back to the node options, select “trigger type : message”

Then I try to select server name and get the “already logging in” error message.

1 Like

I get that error whenever I edit the credential for the discord bot. When this happens, I delete the full credential and create one from scratch, could be with the same exact information.

I noticed that after some time tinkering the node has a tendency of running multiple times. IE: the text trigger is triggered multiple times causing multiple responses. I am assuming that either the node or n8n is not deactiving correctly and with every update a new instance is running. There error is staing its already logging in, probably cause of the prior instances runningi in the background has priority.

It works;

Thank you so much for such a simple and efficient solution :slight_smile:

1 Like

Hi,

Here is what I experience with the Discord Voice Trigger node (v0.19.0):

The voice recording works fine on the bot side — the file gets saved to disk
with correct duration and size — but the audioData field is always null, and
the workflow receives “No audio buffer received!” every time.

My setup:

  • n8n version: 2.8.3
  • Node: n8n-nodes-discord-trigger-new v0.19.0
  • The filePath field is correctly populated (e.g. recordings/userid_timestamp.ogg)
  • The file exists on disk and has valid content
  • audioSize is always 0 and audioData is always null

As a workaround I am currently reading the file from disk using the filePath
field, but the built-in transcription (OpenAI Whisper) does not work either
since audioData is null.

Questions:

  1. Has anyone found a working solution for this?
  2. Is a fix planned, and if so, when can we expect it?

Thank you for the great work on this node!