Edit Fields (Set) consultants

Q: What does the Edit Fields (Set) node do in n8n?

The Edit Fields node modifies the data that flows through a workflow. It can add new fields with static or dynamic values, rename fields to match the requirements of downstream systems, delete fields you don't need, and overwrite existing field values. It's the standard way to reshape data between nodes in an n8n workflow.

Q: Can the Edit Fields node reference data from earlier nodes in the workflow?

Yes. You use n8n expressions (written in JavaScript-like syntax) to pull values from any earlier node's output. For example, you can set a field's value to the output of an HTTP Request node three steps back. This is how you combine data from multiple sources or transform values using string functions, math operations, or conditional expressions.

Q: How do you use the Edit Fields node to strip sensitive data?

Set the node to 'Keep Only Set' mode, and define only the fields you want to pass downstream. Any fields not explicitly included are dropped. This is useful when you're receiving data that contains sensitive information (like credit card numbers or personal details) that shouldn't be sent to the next system in the workflow.

Q: When should you use the Edit Fields node versus the Function node?

Use Edit Fields for straightforward field mapping, renaming, and value setting. Use the Function node when you need complex data transformations that involve loops, conditional logic, array manipulation, or operations that go beyond what n8n expressions can handle. Edit Fields is faster to configure and easier to maintain for simple transformations.

Q: Can the Edit Fields node handle arrays and nested objects?

Yes, but with some limitations. You can reference nested properties in expressions (like $json.address.city) and set nested output fields. For more complex operations on arrays, like filtering, mapping, or reducing arrays within items, the Function node or Code node is usually a better choice. The Edit Fields node works best with flat or lightly nested data structures.

We can help you automate your business with Edit Fields (Set) and hundreds of other systems to improve efficiency and productivity. Get in touch if you’d like to discuss implementing Edit Fields (Set).

Get in touch

Book a call

About Edit Fields (Set)

The Edit Fields (Set) node in n8n reshapes data as it moves through a workflow. It lets you add new fields, rename existing fields, remove fields you don’t need, and set field values using static text, expressions, or references to data from previous nodes. It’s the primary tool for transforming data between the format one system outputs and the format another system expects.

This node solves a core automation problem: different systems use different field names and data structures. Your CRM calls it “company_name” but your invoicing system expects “organisation.” Your form tool sends a full name in one field but your email platform needs separate first and last name fields. The Edit Fields node handles these transformations without writing code.

Common uses include mapping API response fields to the format required by the next node, stripping sensitive fields before passing data downstream, combining values from multiple fields into a single output, and setting default values for optional fields. You can also use it to build entirely new data objects from scratch using expressions that reference data from any earlier node in the workflow.

At Osher, the Edit Fields node appears in virtually every workflow we deliver. Data mapping and transformation are part of every system integration and data processing project. Our BOM weather data pipeline used Set nodes extensively to reshape API responses before loading them into the client’s data warehouse.

If your automation needs to transform data between systems, talk to our n8n team about building clean, maintainable data mapping workflows.

Edit Fields (Set) FAQs

Frequently Asked Questions

Common questions about how Edit Fields (Set) consultants can help with integration and implementation

What does the Edit Fields (Set) node do in n8n?

What is the difference between ‘Set’ mode and ‘Edit Fields’ mode?

In older n8n versions, this was called the Set node. The current version calls it Edit Fields (Set) and offers two modes. In ‘Manual Mapping’ mode, you define each output field individually and set its value. In ‘JSON Output’ mode, you write a JSON expression that defines the entire output structure. Manual Mapping is easier for simple transformations; JSON Output gives more control for complex reshaping.

Can the Edit Fields node reference data from earlier nodes in the workflow?

How do you use the Edit Fields node to strip sensitive data?

When should you use the Edit Fields node versus the Function node?

Can the Edit Fields node handle arrays and nested objects?

How it works

We work hand-in-hand with you to implement Edit Fields (Set)

As Edit Fields (Set) consultants we work with you hand in hand build more efficient and effective operations. Here’s how we will work with you to automate your business and integrate Edit Fields (Set) with integrate and automate 800+ tools.

Step 1

Process Audit

We document the data formats used by each system in your integration: field names, data types, required versus optional fields, and nested structures. For Edit Fields planning, this means creating a field-by-field mapping table that shows how data from the source system needs to be transformed to match the target system’s requirements.

Step 2

Identify Automation Opportunities

We identify where manual data transformation is happening in your current process. Every time someone copies data from one system, reformats it, and pastes it into another, that’s a candidate for an Edit Fields node. We also look for data quality issues caused by inconsistent field formatting that automated transformation can fix.

Step 3

Design Workflows

We design the data transformation layer of the workflow, specifying exactly which fields need to be added, renamed, removed, or transformed at each stage. For workflows connecting multiple systems, we plan the Edit Fields node placement to ensure data is in the correct format before it reaches each downstream node.

Step 4

Implementation

We configure Edit Fields nodes in the workflow with the correct field mappings, expressions, and transformation logic. Each node is tested with sample data from the actual source system to verify that field names, data types, and value formats match what the target system expects. We use ‘Keep Only Set’ mode where appropriate to ensure clean data output.

Step 5

Quality Assurance Review

We test the data transformation with edge cases: empty fields, unexpected data types, special characters, very long strings, and null values. We verify that the output matches the target system’s requirements exactly, including field name casing, date formats, number precision, and encoding. We also check that no sensitive data passes through unintentionally.

Step 6

Support and Maintenance

When source or target systems change their data formats (new fields, renamed fields, changed data types), we update the Edit Fields node configuration to match. We also refine transformations based on production data patterns that weren’t apparent during initial testing, such as new edge cases or format variations.

Transform your business with Edit Fields (Set)

Unlock hidden efficiencies, reduce errors, and position your business for scalable growth. Contact us to arrange a no-obligation Edit Fields (Set) consultation.

Get in touch

Book a call