Edit Fields (Set)

processing.set Processing v0.1.0

Set output fields from literals or JS {{ }} expressions, per item. Choose which other input fields to keep (all/none/selected/except); expressions can reach into JSON held in a string.

The Edit Fields (Set) step on the Studio canvas — The **Edit Fields (Set)** step as it appears on the Studio canvas — input pins on the left, output ports on the right.

Finding it in the library

Search the builder's node library for Edit Fields (Set) (it lives under Processing). A single click opens the in-editor docs panel shown here — description, ports, and every property, without leaving the canvas. Double-click (or drag) to add it to the workflow.

Edit Fields (Set) in the node library, with the in-editor docs panel open — The library entry and the in-editor docs panel for **Edit Fields (Set)** — the same reference this page is generated from.

Wired up in the builder

Edit Fields (Set) in a real, runnable flow — captured live from the Studio editor, exactly as it looks on your canvas. This is the same workflow used for the example input & output below.

Edit Fields (Set) wired into a runnable workflow in the Studio builder — **Edit Fields (Set)** wired into a runnable flow — input on the left, output on the right.

How it’s configured

The node’s Configure panel as it opens in the builder when you select the step — every setting laid out with real values. Click any field to edit it.

The Edit Fields (Set) node's Configure panel in the Studio builder — The **Configure** panel for **Edit Fields (Set)**, showing the settings from the flow above.

Ports

Ports are the node’s contract with its neighbours. In the editor a port label renders bold when wired and italic when optional; ◈ ports accept attachment carriers rather than data wires.

Direction	Port	Label	What flows through it
Input	`input`	Input
Output	`output`	Output

How data flows through it

Edit Fields (Set) consumes the content of the incoming envelope — when it is fed directly by a trigger, the trigger’s wrapper is unwrapped at the node boundary so the node sees the actual data, not the metadata shell. Its output becomes the payload for the next node, while the envelope (trace ids, correlation, binary refs) rides along untouched. In the Runs view you always see the whole envelope for both sides of this node.

Expressions in the config

None of this node’s properties are string-typed, so {{ }} expressions don’t apply here — JSON- and code-typed fields are always taken literally.

Build it with AI

Every node in this reference is reachable through Flowdrome’s AI Copilot and the MCP tools — say what you want, and the graph surgery happens server-side. Node types resolve fuzzily, so the catalog label (Edit Fields (Set)) works as well as the exact type id (processing.set).

In the Copilot panel (or any connected AI):

add a edit fields (set) node after the trigger

As a step in a create_chain_workflow call:

{"type":"Edit Fields (Set)","config":{}}

Raw MCP call — add this node to a workflow with add_node

curl -s -X POST http://localhost:48170/mcp -H "content-type: application/json" -d '{ "jsonrpc": "2.0", "id": "1", "method": "tools/call", "params": { "name": "add_node", "arguments": { "workflowId": "<id>", "type": "Edit Fields (Set)" } } }'

Example input & output

Captured from a real test run of the workflow above — this is what you see in the run data panel after pressing Test workflow.

Input — what the node received

The Edit Fields (Set) node's input envelope in the run data viewer — The input envelope in the Runs view — Flowdrome always shows the whole envelope, with the payload inside `body`.

Output — what the node produced

The Edit Fields (Set) node's output envelope in the run data viewer — The output envelope after the step ran.

Property reference

Every setting, with its type and default — the same fields shown configured in the panel above.

Property	Type	Default	Description
Mode `mode`	`select`	`"manual"`	Manual mapping = define fields one by one. JSON = produce the whole output object from JSON / a {{ }} expression. `jsonmanual`
Fields to set `assignments`	`set-fields`	`[{"name":"","type":"string","value":""}]`	Each field has a name (dot-notation builds nested objects), a type, and a value. The value can be a literal or a JS {{ }} expression like {{ $json.body.results[0].name.first }} or {{ $json.total * 2 }} — expressions can reach into JSON held in a string (e.g. an HTTP body). Shown when `(mode ?? "manual") === "manual"`
JSON output `json`	`json`	`{}`	The output object. Values may be {{ }} expressions, e.g. { "name": "{{ $json.first }}" }. Shown when `mode === "json"`
Other input fields `include`	`select`	`"all"`	Which fields from the input to keep alongside the ones you set. Set fields always override. `allexceptnoneselected`
Fields to keep `includeFields`	`field`	`—`	Comma-separated field names/paths to keep from the input (empty = keep none of the others). Shown when `include === "selected"`
Fields to drop `excludeFields`	`field`	`—`	Comma-separated field names/paths to remove from the input (empty = drop none). Shown when `include === "except"`
Dot notation `dotNotation`	`boolean`	`true`	Interpret dots in a field name as a nested path (user.name → { user: { name } }). Off = use the whole name literally.
Ignore type conversion errors `ignoreConversionErrors`	`boolean`	`false`	If a value can't be converted to its chosen type, keep the raw value instead of failing the node.

Using it

Manual mapping with expressions

In manual mode the properties panel shows an assignments table — one row per field you want to write. Each row has a name, a type, and a value, and the value takes {{ }} expressions:

Name	Type	Value
`customer.name`	string	`{{ $json.body.results[0].name.first }}`
`total`	number	`{{ $json.total * 2 }}`
`processedAt`	string	`{{ $now }}`

Dot-notation names build nested objects (customer.name creates { customer: { name: … } }). The Map from input button pre-fills rows from the last run’s data so you pick fields instead of typing paths.

Include controls what happens to the other input fields: keep all, keep none (only your set fields), keep selected, or keep all except listed ones.

JSON mode — emit the whole object

Switch Mode to json and type the output object into the JSON editor (expressions still work inside values):

{ "name": "{{ $json.first }} {{ $json.last }}", "source": "flowdrome" }

Tips

Expressions descend into JSON-in-a-string. {{ $json.body.results[0].name }} works even when body is a JSON string (an HTTP response) — the expression engine parses it on the way in.
Per-item by nature: over a list input, assignments apply to each item.
Ignore conversion errors keeps the raw value instead of failing when, say, "abc" won’t become a number.
Set is the n8n Edit Fields (Set) equivalent at full parity — if you’re arriving from n8n, your habits transfer.

Related nodes

The rest of the Processing group — the same folder you’d scan in the editor’s library.

This page is generated from the node registry by gen-node-docs.mjs on every site build — ports, properties, defaults and visibility rules cannot drift from the code. The screenshots and example data are captured from a live Flowdrome by npm run shots:nodes and npm run gen:examples. The hand-authored notes above are merged in.