DocumentationWorkflowsLogic and data
Edit Fields (Set) node
Set, rename, or remove fields in the data flow, e.g. reshape a trigger's output into the format the next node expects. Values support templates like {{ $json.user.name }}. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
8 min readUpdated
What this node does
Set, rename, or remove fields in the data flow, e.g. reshape a trigger's output into the format the next node expects. Values support templates like {{ $json.user.name }}.
Use Edit Fields (Set) as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Edit Fields (Set) from the node catalog.
- 02Complete the required fields and map values from previous steps.
- 03Run the node with a small test record and inspect its output.
- 04Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Edit Fields (Set) has one focused purpose. Its available settings appear when you select the node.
Settings
| Field | Meaning | Area |
|---|---|---|
| Set fields | New fields or overrides. Pick the type per row (String, Number, Boolean, JSON). Values support `{{ $json.field }}`. | Standard |
| Import version | Configure this value in the node panel. | Standard |
| Create nested fields | Dots in a field name create nested fields. customer.name stores name inside customer. | Standard |
| Keep value on type errors | Keeps the original value when it does not match the selected type. | Standard |
| Pass files on | Keeps files received together with the input data. | Standard |
| Remove fields | Enter the field names that should go, separate multiple with a comma (e.g. tmp, debug). Runs before new fields are set. | Standard |
| Rename fields | `from` → `to`. Runs before setting. | Standard |
| Keep only set fields | When on: input fields are discarded, only the set fields survive. | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
Example and test run
Set status + counter: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"name": "Alice",
"score": 42
}Access and security
Before activation, review which data enters this step and what its output contains.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.