Hello, I’m searching a way to define variables that could vary through environments (dev, staging, prod°, …) I don’t know how to do this, and didn’t see anything in the documentation or in the forum. Maybe I’m not searching with the good words, but, is there a way to do this ? My need would be t…

You can just use environment variables. So if you set the environment variable: export ASDF=test and you then use the following expression anywhere inside of n8n {{$env['ASDF']}} then it will output test.

Maybe I’ve found a way to do this with the combination of Read Binary File + Spreadsheet + Function nodes. I write my settings in a setting.csv file with a setting;value; header. Each line will contain a key/value pair of setting. The Read Binary will load the file, the spreadsheet transform in a…

Is there a place in the documentation where it was written ? I’m sorry if I missed it.

And if it’s missing, I could make a PR to add some documentation on it, if you guide me where to insert this part.

Currently it is only listed very shortly as part of available variables in Expressions here: [image] Node Basics | n8n Docs n8n is an extendable workflow automation tool that enables you to connect anything to everything via its open, fair-code model.

Is it only support in Function and FunctionItem nodes? I tried in other nodes, it seems not support {{$env[‘ASDF’]}}

Welcome back @Ho_Tommy That should work. Perhaps the link below helps to clarify how to use it. [image] Secrets from env vars and files Feature Requests No, nothing has to be especially exposed to Node.js and also is totally unrelated to convict but maybe there is a misu…

Hi @RicardoE105 , I am using docker and there are only Function and FunctionItem nodes can use $env.my_var, other nodes only can access {{$env.NODE_ENV}}. Please see the image below. Function Item node: [image] Other node: [image]

Hi @RicardoE105 , I found it is only the frontend problem. Actually, It can work properly in backend. Execute Command node front-end showing [not found]: [image] Execute Command node result showing correctly: [image]

Yes, that is correct. It will only display them correctly if you execute the node. To make it also work without executing the node, we have to always send all environment variables to the UI which we want to avoid.

Maybe a silly question but is it possible to define an environment variable during the workflow? Also, is it possible to update it without restarting n8n or reloading the workflow (example: store an access token as an environment variable and refresh it)? Thank you

How to define custom environment variables available in the n8n workflow

Questions

sscarduzio April 7, 2022, 8:20am 14

Apparently this does not work anymore in the latest n8n (installed as npm)

console:

Environment variables not accessible in self-hosted setup - $env returns empty object

Topic		Replies	Views
Environmental variables in workflows Questions	4	133	December 2, 2025
Sharing community node: Environment Variables Built with n8n custom-node , community-node	0	67	January 19, 2026
Not accessible via UI, please run node Questions expressions	3	940	November 6, 2023
How to modify environment variables inside n8n? Questions deployment	5	8949	June 24, 2025
Variables in n8n Questions	10	3297	March 30, 2025

How to define custom environment variables available in the n8n workflow

Related topics