n8n Edit Fields (Set) Node: Modes, Pass-Through Fields, Dot Notation and Types
By Abhishek Patoliya · 2026-08-16
The node older workflows call Set is the one n8n now names Edit Fields (Set). Its job hasn't changed: add, overwrite or remove fields on each item without writing code. It's probably the most-used node in n8n, because so much workflow logic is "reshape this data before the next step". This lesson covers its two modes, the options that cause most surprises (what happens to fields you didn't mention, dot notation, types), and when to use something else.
Before you start: read n8n expressions; most Edit Fields values are expressions. Options below follow n8n's documentation as of 9 November 2026.
Two modes
- Manual Mapping: add fields one by one (or drag them from the input panel), each with a name, a type and a value that is either fixed or an expression. Best for most cases: readable at a glance.
- JSON Output: write the output item as a JSON object, with expressions inside it. Useful for nested structures or building a request body in one place.
// JSON Output mode example
{
"id": "{{ $json.id }}",
"customer": {
"email": "{{ $json.email.toLowerCase() }}",
"plan": "{{ $json.plan }}"
},
"source": "web-form"
}
What happens to the fields you didn't mention
This is the setting that most often surprises people. Edit Fields can either pass every incoming field through and add or overwrite the ones you set, or output only the fields you defined. n8n's docs describe an Include in Output setting that chooses which input data appears in the output, and a Keep Only Set Fields toggle that discards any input data not used in the fields you set. (Older Set node versions show these choices with slightly different labels.)
Input item: { "name": "Acme", "id": 42, "internalNote": "flagged" }
Set: status = "active"
All input fields kept: { "name": "Acme", "id": 42, "internalNote": "flagged", "status": "active" }
Only set fields kept: { "status": "active" }
Keeping only the set fields is the cleaner choice before sending data to an external API, a model prompt or a log: you pass exactly what's needed and nothing that shouldn't leave the workflow (internal notes, personal data). See handling PII and what goes in a prompt.
Dot notation
Support Dot Notation is on by default: a field named number.one with value 20 produces a nested object, {"number": {"one": 20}}. Turn it off and you get a single key with a dot in its name: {"number.one": 20}. Leave it on to build nested JSON from flat fields; turn it off if a target system genuinely expects dots in key names (some analytics and logging tools do).
Types and conversion
In Manual Mapping, each field has a type (in current versions String, Number, Boolean, Array and Object). Setting a field to Number converts "42" to 42, which fixes the string-number problems from the expressions lesson before they reach a comparison or calculation. If a value can't be converted, the node errors unless you enable Ignore Type Conversion Errors (Manual Mapping only). Leave that off while building, so bad data shows up as an error rather than a silently wrong value.
Binary data
Include Binary Data controls whether files attached to the incoming items (PDFs, images from a form or email) are passed on. If a later node can't find a file you know arrived, check this option first. Working with files is covered in binary data in n8n.
Old Set nodes in existing workflows
Workflows built on earlier n8n versions keep their older Set node versions, and they keep working. There's no need to replace them just because of the rename. If you do migrate one (to tidy up, or to use the newer options), change one node at a time and compare the output on the same pinned test data before and after (see pin data), checking especially which fields pass through and how dotted names are handled.
When to use something else
- Combining items (totals, lists): the Aggregate node or Summarize.
- Splitting an array into items: Split Out.
- Merging data from two branches: the Merge node.
- Logic with conditions, loops over nested arrays, or more than one fallback: a small Code node, where you can name variables and test the logic.
Key takeaways
- Edit Fields (Set) is the renamed Set node; old versions in existing workflows keep working.
- Decide deliberately whether other input fields pass through; keeping only the set fields is safer before APIs, prompts and logs.
- Dot notation (on by default) turns
a.b names into nested objects.
- Field types convert values; keep type-conversion errors visible while building.
Exercise: take an item with name, id, internalNote and qty as the string "3". Produce {"order": {"id": 42, "qty": 3}} with no other fields, first in Manual Mapping (using dot notation and a Number type) and then in JSON Output mode. Next lesson: paired items.
References (checked 9 November 2026)
Written by Abhishek Patoliya, Senior n8n Developer & Automation Architect, Surat, India. Verified n8n Creator.