To anyone else having issues with this, some of my students who ran into issues on formatting, we found that when you switched from Expression mode to Fixed mode, the space showed up there, the second they removed it in fixed mode, it all worked. Check to see in BOTH expression mode and fixed mode that there are no spaces. It has to be exact. Give it a try, that’s what worked for a few of my students who were working through course 2. (NOTE: In my programs, we don’t give out exact answers to the students but help them through the course material, the fact that you’re figuring out these issues here, this is equivalent to what we do in real world production situations where things are not working as they should.). Great work on trying to figure it out, you’ll get it done, I believe in you!! KEEP AT IT!!!
Your suggestions about removing linebreaks and additional spaces sound good, but it would not work with my n8n in version 1.105.4. I only could get it to work when I downgraded to n8n 1.82.1 and built the workflow again for that version. After that I could complete the course. My message for the discord node after the gmail node was:
I sent the file using email with the label ID {{$json.labelIds[0]}}. MyID:1234567
(of course I put my unique id instead of “1234567“)
My guess is that this is a bug in the discord node which was introduced in an n8n version after 1.82.1.
I think you have to get the orders ID.
using email with the label ID {{$json.labelIds[0]}}. MyID:1234567
Use
item.binary.data.
No, that didn’t work either. I think $json.labelIds[0] is correct, becaue it is a proof that the email from the previous node was sent. If the email was sent, the label ID is “SENT“.
Also stuck here, do you mind explaining how you finally worked it out?
I downgraded my n8n instance to version 1.82.1, built the workflow again for that version and it succeeded.
See here:
Hey Folks,
Apologies for the delay, have been pretty busy last few weeks, so couldn’t give you any updates.
So far I was able to determine few things for my certain situation
- It turned out I am using selfhosted version (not the cloud one) for which I do apologize, I was left with the impression I am on the cloud ver, but this is because how its setup for the current organization.
- I got some valuable info for the selfhosted versions, for anyone running selfhosted version and its running on its organizations infrastructure it most likely won’t run because of the internal company routing and api access rules . If you are running the instance on your home devices and all connections are allowed the already mentioned ideas and workarounds in this topic should work.
I am marking this as resolved since I cant change my copany policy/rules and hence make it working for myself.
Thanks to all!
I also experienced an issue with the Discord node.
I tried lots of things and even considered downgrading my version, but ultimately I think the N8N team has strict rules for validating the messages we send.
For me, it was the space between ‘ID’ and my ID; for you, I think it was the same. Downgrading your version is one solution, but I think the Discord node works properly. In my opinion, it was right.
You are right, I tried again with n8n 1.107.4. A space between “My ID:“ and my unique ID made both discord nodes work as expected.
Hi guys, got the same issue on 21/08/2025, for me it worked with the following steps : 1- update the credentials with https://internal.users.n8n.cloud/webhook/discord-level2 as the new webhook credentials, 2- go to admin panel > manage > set n8n version to 1.107.4 (latest stable) or at least any further stable version 3- use the folowing expression as a message : “I sent the file using email with the label ID {{ $json.threadId }}. My ID: {{ $(‘HTTP Request1’).params[“headerParameters”][“parameters”][0][“value”] }}” Hope to see you certified soon 
Self hosted, latest version as of right now. Did it with this in expression mode:
I sent the file using email with the label ID {{$input.item.json.labelIds[0]}}. My ID: 835a183c0c1ee72da94b5818c5091859