Create code expression for other node - Text Course 1 - bug?

On this page

…in the box “Constructing your own message” it says

To add the Unique ID portion of the statement, you'll need to expand Nodes > HTTP Request > Parameters > headerParameters > parameters > [Item: 0] and select the value.

There is no “Nodes” text on the page.
From where do I get the code for the expression if I don’t just want to copy-paste it?

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

You can see it with Edit Fields node and building an expression like:
{{ $('nodename').params }}

But it’s a very rare case when you need it.

Thank you for the reply.
If it’s super rare I don’t see the point of teaching it in course level 1 to be honest.
What you mean is that it’s rare that you reference the input of an HTTP request in a different node, right?

However your reply doesn’t answer the question how to get these types of inputs via GUI as described on the mentioned page of the course.
Someone in the Discord mentioned that this is actually outdated.
So I’ve created a bug report on GitHub as well.

No, accessing another node’s output is a common scenario. but accessing the .params property of a node is very rare. It’s a special variable that holds the chosen options of the desired node. That information is not needed in 99% of cases. Dunno why it’s in the course. Actually, the course has been written a while ago, so it’s a question to @bartv :grin:

You can check more of the special variables there: Output of other nodes | n8n Docs

You can’t expand them via GUI :slight_smile:
maybe it was possible previously, but currently, as I know, there is no way to do so.

2 Likes

Thanks again @barn4k
You are right.
The text courses - both - are embarrassingly outdated for such a hyped company/product from my point of view.
I’ve added several bug-reports and a small fix to the GitHub repo.

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