Type something like {{$json.email}} into a field in n8n, and rather than a fixed value, that field pulls in dynamic data from elsewhere in the workflow - that’s an expression, a short piece of code inside double curly braces that a node can evaluate at runtime. It can reach into the current item, an earlier node, a workflow variable, or run a built-in function to reshape data, like formatting a date or joining text together.
Example
Instead of typing a fixed name into an email node’s subject line, you could write something like “Hi {{$json.firstName}}, your order is confirmed” so each email pulls the right name from an earlier node automatically, for every item that passes through.
n8n relevance
Expressions are one of the most important skills to pick up in n8n, because they’re what turn a rigid, one-off automation into something that adapts to whatever data flows through it. You’ll use them constantly - pulling in fields from earlier nodes, building dynamic prompts for AI nodes, constructing URLs for API calls, applying conditional logic. n8n training spends real time on expression syntax specifically, since knowing it is what separates someone who can follow a template from someone who can build and debug workflows from scratch.