How many n8n templates use the Edit Fields (Set) node?

7,554 of the 13,574 public templates on n8n.io (55.7%), in our snapshot of 2026-10-20.

What is the Edit Fields (Set) node most often used with?

Code, which appears in 61.7% of its templates.

What is the difference between the Set node and Edit Fields?

Same node, renamed. The internal type is still n8n-nodes-base.set, which is why template JSON still says set.

Should I use Edit Fields or Code to reshape data?

Edit Fields for renaming, adding and dropping fields; Code when you need loops, conditions or calculations across items.

RecipeAgents / n8n nodes / Edit Fields (Set)

Node reference · data pulled Oct 26, 2026

n8n Edit Fields (Set) node: what the data shows

Adds, renames, overwrites or drops fields on every item, with no code.

7,554public templates use it (55.7% of 13,574)

58.1%of those also contain an AI node

51.3score out of 80 · rank 16 of 22

68commits to its source folder on GitHub

What it does

Older workflows and many tutorials call it the Set node; the editor now shows Edit Fields. You either map fields one at a time in the form (often by dragging from the input panel), or write the whole output as JSON with expressions. A separate setting decides whether the rest of the incoming data travels along or is thrown away.

It is the second most common node in the public library because nearly every workflow needs to rename or tidy something between two apps. If you find yourself writing a Code node only to rename keys, this node is the lighter choice.

How often public templates use it

7,554 of the 13,574 public templates on n8n.io (55.7%) contain this node, in the snapshot we took on 2026-10-20. The table splits that by the year each template was published. 2026 runs to October 20.

Year published	Templates with the node	Share of that year
2024	297 of 462	64.3%
2025	3,369 of 6,564	51.3%
2026	3,682 of 5,845	63.0%

The median template using this node has 208 views on n8n.io, against 284 for all templates. Template counts show what people publish, not what runs in production.

What it is used with

The most frequent partners are the nodes that appear most often in the same templates. "Lift" compares that with the whole library: 2× means the partner turns up twice as often next to this node as in an average template.

Most frequent partner	Share of its templates	Lift
Code	61.7%	1.04×
HTTP Request	58.0%	1.12×
If	57.4%	1.14×
Google Sheets	36.6%	1.03×
Schedule Trigger	35.3%	1.11×
AI Agent	33.4%	1.07×

No partner clears our strong-pairing bar (in at least 5% of its templates and 1.5× the library rate). That is typical of nodes used almost everywhere: they sit next to everything about as often as average.

Most viewed public templates that use it: Creating an api endpoint (464,784 views); Automate multi platform social media content creation with ai (442,651 views); Angie personal ai assistant with telegram voice and text (429,283 views).

Versions and changes

Node versions from the npm packages n8n-nodes-base and @n8n/n8n-nodes-langchain, version 2.44.4. New workflows get the default version; workflows built earlier keep the version they were built with until you replace the node.

Node	Versions	Default	Credential types	Scope
Edit Fields (Set)	1, 2, 3, 3.1, 3.2, 3.3, 3.4, 3.5	3.5	none needed	–

Source on GitHub: packages/nodes-base/nodes/Set: 68 commits since the repository was reorganised on 2021-11-17, last on 2026-10-01.

Recent fixes and features

2025-09-10: fix(Set Node): Handle special replacement patterns in JSON expressions (PR #18162)
2024-10-15: fix(Set Node): Fix issue with UI properties not being hidden (PR #11263)
2024-06-18: feat(Set Node): Preserve binary data by default (PR #9668)
2024-01-05: fix(Set Node): Field not excluded if dot notation disabled and field was set by using drag-and-drop from ui (PR #8233)
2023-10-12: fix(Set Node): Null should not throw an error (PR #7416)
2023-10-03: fix(Set Node): Do not stringify null and undefined (PR #7313)

Merged dates from GitHub. A fix only helps once your n8n instance runs a release that includes it, so check your version.

Known problems

Fields vanish after the node. If you tell it to keep only the fields you set, everything else from the input is dropped, including IDs later nodes need. Check the Include in Output setting. Source: n8n docs
Dots in names create nested objects. A field named a.b becomes {a: {b: ...}} by default. Turn off Support Dot Notation if you want the literal key. Source: n8n docs
Binary data behaviour changed. Since mid-2024 the node keeps incoming binary data by default; older node versions dropped it. Source: n8n PR #9668
$ patterns inside JSON mode. Special replacement patterns in JSON-mode expressions were mishandled until a 2025 fix. Source: n8n PR #18162

Forum trouble signal: not measured. The n8n community forum's terms forbid automated access, so we don't count forum threads.

Our recipes that use it

None of our 25 recipes uses this node yet. Browse all of them on the free n8n templates page.

Official docs and sources

n8n docs: Edit Fields (Set)

Usage, pairings, AI share and views: our count of 13,574 public n8n.io templates (snapshot 2026-10-20). Versions: npm packages, version 2.44.4. Changes: n8n's GitHub repository. Docs read and data pulled Oct 26, 2026. We describe each node in our own words; the docs are the authority on settings.

Related nodes

Questions

How many n8n templates use the Edit Fields (Set) node?: 7,554 of the 13,574 public templates on n8n.io (55.7%), in our snapshot of 2026-10-20.
What is the Edit Fields (Set) node most often used with?: Code, which appears in 61.7% of its templates.
What is the difference between the Set node and Edit Fields?: Same node, renamed. The internal type is still n8n-nodes-base.set, which is why template JSON still says set.
Should I use Edit Fields or Code to reshape data?: Edit Fields for renaming, adding and dropping fields; Code when you need loops, conditions or calculations across items.