How to Use the n8n Edit Field Set Node Easily 2026

Opening n8n lands you on the Overview page, listing every workflow you have access to alongside execution stats like production executions, failure rate, and average run time. An account with some history might already show a couple of workflows, a research pipeline, an AI chat flow, while a brand-new one will be empty aside from the Create workflow button. Either way, this is the starting point before you build or edit anything.

Inside a fresh workflow, the canvas offers two starting points: "Add first step," which opens the manual node picker, or "Build with AI," which opens a chat panel where you describe what you want automated and n8n suggests a starting structure. For learning exactly what the Edit Fields node does, Add first step is the more direct route: it lets you place and configure nodes one at a time instead of accepting a generated flow.

Every workflow needs something to start it, so the first node picker you'll see is "What triggers this workflow?" with options like Trigger manually, On a schedule, On webhook call, On form submission, and When executed by another workflow. For testing the Edit Fields node in isolation, Trigger manually is the simplest choice: it runs the flow on a button click in the editor, described right in the picker as good for getting started.

With a trigger in place, search for and add Edit Fields to the canvas, then open it to see its Parameters tab. The first setting is Mode, with two options: Manual Mapping, described as editing item fields one by one, and JSON, for customizing the item's output with raw JSON instead. Manual Mapping is the more approachable option for straightforward field changes; JSON mode is faster once you're comfortable writing the data structure directly.

In Manual Mapping mode, the node shows a drop zone for input fields plus an "Add Field" link. Click it to define a field name, type it as a string, number, boolean, or object, and set its value, either typed directly or pulled from an upstream node through an expression.

A toggle controls whether fields you haven't explicitly touched still pass through to the output. Depending on your n8n version this shows up as "Include Other Input Fields," or, in current n8n documentation, as "Keep Only Set Fields" alongside a separate "Include in Output" setting.

The naming has shifted, but the effect is the same: deciding whether only the fields you've defined here survive, or everything else rides along too. One setting is easy to miss: field names support dot notation by default, so a field named "address.city" creates a nested address object with a city key, not a single field literally called address.city. If that's not what you want, look for "Support Dot Notation" in the node's Options and turn it off.

If you need to restructure a payload more heavily than a handful of individual fields allows, switch Mode to JSON and write or paste the output structure directly, referencing upstream data with the same expression syntax n8n uses elsewhere. This is usually faster for nested objects or arrays than building the same structure field by field in Manual Mapping.

The node's Input and Output panels sit on either side of the parameters and start out showing "No input data" and "No output data" until you run something through them. Click "Execute previous nodes" to pull real data in from whatever comes before Edit Fields on the canvas, or use "Execute step" to run the node itself and see your configured fields in the Output panel, confirming the shape is correct before you connect anything downstream.