n8n-expression-syntax

Fix n8n expression syntax errors by enforcing proper {{}} usage and safe data access. Use bracket notation for spaces, .body for webhook payloads, and exact node-name casing to prevent common workflow mistakes.

n8n expressions fail with spaces in node names if you use dot notation. You must use bracket notation, like $node["My Node"].data, to correctly parse complex paths and spaces in your workflow references.

Reference data from other nodes in n8n by using exact node-name casing and proper syntax. Ensuring the node name matches exactly prevents data retrieval errors during workflow automation execution.

The correct syntax for n8n expressions requires wrapping dynamic data in double curly braces, like {{ }}. Enforcing proper {{}} usage guarantees the workflow evaluates variables safely and prevents output formatting issues.

Debug common n8n expression mistakes by testing simple values in the expression editor preview. Verify webhook .body access, exact node-name casing, and bracket notation for spaces to resolve typical workflow automation errors.

Yes, n8n expression syntax requires exact node-name casing for references. Using incorrect capitalization when pointing to other nodes will fail to retrieve data, breaking your workflow automation reliability.