What does the Edit Fields node do in n8n?
Quick answer
The Edit Fields node, called Edit Fields (Set) in n8n and once just Set, shapes the data that moves between steps. You list the fields you want, give each a name and a value or an expression, and the next node gets exactly those fields instead of everything the trigger sent.
Last updated
Take the free module →Module 4 of the free n8n Jump Start course, about 6 minutes. No account needed.
Updated · By Robert Breen
Why it matters for a small business
A form, an email or an API call usually sends more than you need, often buried a level down. If every later step digs through that raw data, one changed field name breaks three nodes. Picking the fields once, near the start, gives the rest of the workflow one tidy shape to rely on.
It is also where most "blank column" problems get fixed. When a sheet row comes out with an empty cell, the usual cause is that no field carries that value yet. You add it in Edit Fields, test, and publish again.
In a real lesson: n8n: Execute Step, Execute Workflow and Publish
In the Execute step, Execute workflow and Publish lesson, Maple Street Bookkeeping, a made-up office, gets new-client forms through a Webhook. Edit Fields sits in the middle in Manual Mapping mode, and under Fields to Set it picks out email and name with {{ $json.body.email }} and {{ $json.body.name }}, because the form data arrives inside body.
After Execute workflow, row 2 of the New clients sheet has the email and name, but Service is blank. You open Edit Fields, click Add Field for service = {{ $json.body.service }}, and then click Publish again, because the live workflow is still the old version.
Try this lesson free or read the step-by-step guide.
How AI helps
When the incoming data is a wall of nested JSON, I paste one sample into ChatGPT or Claude and ask: "Which expression gets the client's email from this?" It usually answers with the path, such as $json.body.email, and I check it in the INPUT panel before I trust it. Practice the clicks in the Execute and Publish lesson.
Common confusions
Edit Fields vs field mapping in the Sheets node
Edit Fields shapes the data for every later step. Field mapping in a Google Sheets node only decides which value lands in which column of that one sheet.
Fields you set vs fields that pass through
By default the node sends on only the fields you set. Turn on Include Other Input Fields if later steps still need the rest.
Tips
- Name fields the way your sheet's headers are named, so mapping is automatic.
- Run Execute step on this node first and read the OUTPUT before you test the whole workflow.
Related terms
More n8n and automation terms
Where you use it: free lessons
- n8n: Execute Step, Execute Workflow and Publish (n8n, 6 min)
- Litescrape in n8n: Swap SerpApi for a Cheaper Search API (n8n, 7 min)
- n8n: What Is n8n? Build Your First Workflow (n8n, 8 min)
- n8n: Items, JSON and Expressions, Explained by Doing (n8n, 9 min)
Frequently asked questions
- What is the Set node in n8n?
- It is the old name for Edit Fields (Set). The job is the same: choose, rename or add the fields the next step receives.
- Why does my n8n Edit Fields node drop my other fields?
- By default it outputs only the fields you set. Turn on Include Other Input Fields to keep the rest of the incoming data.
- Do I need to publish again after changing Edit Fields?
- Yes. The change is saved in the editor, but real runs use the published version until you click Publish again.