Can I use n8n expression syntax inside a Code node?

No, n8n Code nodes use standard JavaScript. You should use direct variable access like $json.field or the $input API instead of curly brace expressions.

How do I correctly access webhook data in an n8n workflow?

In n8n, webhook data is wrapped in a .body property to preserve headers and query params. Use {{$json.body.fieldName}} instead of {{$json.fieldName}}.

How do I reference a node name that contains spaces?

When a node name has spaces, you must use bracket notation and quotes: {{$node["My Node Name"].json.field}}.

Why is my n8n expression returning literal text instead of data?

This usually occurs when you forget to wrap your expression in double curly braces. Ensure your code looks like {{$json.field}} rather than just $json.field.

n8n Expression Syntax Validator

Name: n8n Expression Syntax Validator
Author: Gingi892

byGingi892

Productivity & Workflow

Validates and fixes n8n expression syntax to ensure reliable workflow automation and data mapping.

About

This skill provides a comprehensive validation framework and expert guide for writing correct n8n expressions within automated workflows. It helps developers master the double curly brace syntax, correctly reference data from previous nodes using $node, and navigate the specific data structures of webhook triggers. By identifying common pitfalls like missing braces, case-sensitivity issues, and incorrect usage in Code nodes, this skill ensures that your n8n workflows execute without data mapping errors or runtime failures.

Key Features

Validates double curly brace syntax for dynamic n8n fields
0 GitHub stars
Distinguishes between expression syntax and direct JavaScript Code node logic
Provides templates for Luxon-based date formatting and manipulation
Standardizes node references including bracket notation for spaces
Fixes common webhook data access errors by mapping to the .body property

Use Cases

Troubleshooting 'undefined' errors when mapping data between n8n nodes
Formatting dynamic timestamps and generating relative dates for automation
Accessing nested JSON data from webhooks and HTTP request triggers

About

Key Features

Validates double curly brace syntax for dynamic n8n fields
0 GitHub stars
Distinguishes between expression syntax and direct JavaScript Code node logic
Provides templates for Luxon-based date formatting and manipulation
Standardizes node references including bracket notation for spaces
Fixes common webhook data access errors by mapping to the .body property

Use Cases

Troubleshooting 'undefined' errors when mapping data between n8n nodes
Formatting dynamic timestamps and generating relative dates for automation
Accessing nested JSON data from webhooks and HTTP request triggers