Built for n8n Community & Self-Hosted Engineers

n8n Expression Studio & Webhook Formatter

Extract dot-notation JSON paths, generate Luxon date formulas, build schedule crons, and construct bulletproof expressions for your workflows.

✓ n8n v1.0+ Syntax • ✓ Luxon DateTime Engine • ✓ Recursive JSON Parser • ✓ Visual Cron Builder

n8n Expression Studio v2.4

• 100% Client Engine

Select Common Expression Pattern

Customize Node or Property Parameter

Changes the active field key in the expression above.

Evaluated n8n Expression Valid n8n v1+ Syntax

Simulated Runtime Value

user_10492@enterprise.com

Copyable Expression Token

Production Workflow Automation

Built for n8n Workflow Architects

Eliminate syntax errors, invalid date parsing, and broken object references in high-throughput enterprise pipelines.

Native Luxon Support

Pre-built DateTime formulas mirror n8n's internal Luxon engine for reliable timezone offsets.

Deep Path Traversal

Recursive webhook inspector traverses complex nested arrays and payload objects seamlessly.

⚒

Predecessor Selectors

Easily format $('NodeName').item.json syntax without typing manual index chains.

⏱

Crontab Validator

Human-readable schedule translation prevents unintended minute-loop triggers.

Integration Guide

3 Steps to Flawless n8n Expressions

Select Recipe Pattern

Choose between current node access, previous node lookups, or Luxon DateTime transformations.

Inspect Live Output

Check the simulated output to verify date formatting, string interpolations, and key naming.

Paste Into Node Field

Click to copy the double curly bracket expression and paste directly into your n8n node parameters.

Architecture Documentation

n8n v1+ Expression Engine & Item Linking Standards

Author: n8n Universe Engineering Team • Updated October 2026

In n8n version 1.0 and higher, the expression engine relies on paired-item data resolution. Unlike legacy versions where node executions passed arbitrary flat arrays, modern n8n enforces strict item-to-item mapping:

1. The $json Namespace

The $json variable is shorthand for the current item currently flowing through the executing node:

2. Referencing Predecessor Nodes

To access data produced by upstream nodes without breaking item pairing, use the node selector function:

By using .item rather than .first(), n8n maintains item lineage across multi-item iterations.

Browse all technical guides →

Got Questions?

Frequently Asked Questions

What syntax does n8n use for expressions in v1.0+? ▾

n8n v1.0+ uses double curly brackets '{{ ... }}' with JavaScript evaluation. Common variables include $json for current item data, $now for Luxon DateTime operations, and $('NodeName') for referencing predecessor nodes.

How do I format dates in n8n workflows? ▾

n8n bundles the Luxon DateTime library. You can use expressions such as {{ $now.toFormat('yyyy-MM-dd') }} or {{ $now.plus({ days: 7 }).toISO() }} directly in input fields.

How do I reference data from a specific previous node? ▾

Use the node selector expression: {{ $('Webhook').item.json.body.user.email }} or {{ $('Google Sheets').first().json.rowId }}.

Is this n8n tool compatible with self-hosted instances? ▾

Yes. All expressions, cron schedules, and webhook path patterns generated by n8n Universe are 100% compliant with both n8n Cloud and self-hosted Docker/npm instances.