Bug: Discord v2 node crashes with “Cannot read properties of undefined”

Questions
, , ,
1

Hi team,
I’m encountering a consistent crash in the Discord v2 node when used with the Error Trigger node in n8n Cloud (version 1.103.2).

:lady_beetle: Error:

TypeError: Cannot read properties of undefined (reading ‘error’)
at ExecuteContext.parseDiscordError
at sendLegacy.operation.ts:153
…

:repeat_button: Steps to reproduce:

  1. Use Error Trigger node in a workflow.
  2. Connect it to a Discord v2 node (Webhook → Send a Message).
  3. Include dynamic variables such as:
    • {{ $json.execution.error.message }}
    • {{ $json.execution.lastNodeExecuted }}
    • {{ $json.execution.url }}
  4. Trigger a failing workflow.
    :collision: Despite rendering the preview correctly, the Discord node fails and the workflow crashes with:

sendLegacy: undefined

:paperclip: Additional context:

  • n8n Cloud version: 1.103.2
  • Using Webhook credentials with a valid Discord webhook URL.
  • Stack trace shows the error occurs at parseDiscordError() when trying to access .error on an undefined response object.
  • When switching to Discord v1 node, everything works correctly.

:white_check_mark: Temporary Workaround:

Use the older Discord v1 node instead of v2.

Let me know if I can provide a minimal reproducible example, full logs, or screenshots.
Thanks in advance!
— Laura

2

how to use discord 1 node?

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.