Use this node to prepare fields expected by an action: rename data, add text or limit the data passed on. Each row assigns a name to a value; enable Mapped fields only (mappedOnly) to leave unwanted fields out of the output.
With manual input { "name": "Ada", "amount": 120 }, enable this option and add:
A standalone expression preserves its type in the output; combining text and an expression produces text. A dotted name builds a nested object.
With mappedOnly disabled, output preserves upstream fields and adds prepared fields plus items, assigned and vars. With it enabled, these metadata fields are not added: read nodes.set1.amount directly, rather than nodes.set1.vars.amount.
Simple names also create textual global variables, accessible through {{ vars.amount }} or {{ amount }}. To preserve a number, object or array, use the node output. Dotted names such as customer.name do not create a global variable.
Technical type : set. Runtime : nodulz.
Credentials and prerequisites
This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.
See the credentials guide if a remote source or execution target requires access.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
Parameter
Type
Default
Values / limits
fields
array
[]
-
fields[].name
string
-
-; min 1
fields[].value
string
-
-
mappedOnly
boolean
false
-
Configuration help
mappedOnly Mapped fields only
When enabled, the output contains only the fields defined below. When disabled, upstream data is kept and merged with the mapped fields.
fields Variables
Each row assigns a variable name to a resolved value.
Examples
Name: userId
Value: {{ nodes.http1.body.id }}
Read later: {{ userId }} or nodes.set1.vars.userId
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
json
{"fields":[]}
Verification
Check that amount is a number in the inspector and customer is an object. Toggle mappedOnly to observe preserved fields and added metadata. In the next node, select the field through mapping instead of assuming it is under vars. The complete tutorial uses this output in an IF.
Modify, add, or remove item fields
Usage and specifics
Use this node to prepare fields expected by an action: rename data, add text or limit the data passed on. Each row assigns a name to a value; enable Mapped fields only (
mappedOnly) to leave unwanted fields out of the output.With manual input
{ "name": "Ada", "amount": 120 }, enable this option and add:customer.name, value{{ input.name }}.amount, value{{ input.amount }}.message, valueHello {{ input.name }}.Expected output:
{ "customer": { "name": "Ada" }, "amount": 120, "message": "Hello Ada" }A standalone expression preserves its type in the output; combining text and an expression produces text. A dotted name builds a nested object.
With
mappedOnlydisabled, output preserves upstream fields and adds prepared fields plusitems,assignedandvars. With it enabled, these metadata fields are not added: readnodes.set1.amountdirectly, rather thannodes.set1.vars.amount.Simple names also create textual global variables, accessible through
{{ vars.amount }}or{{ amount }}. To preserve a number, object or array, use the node output. Dotted names such ascustomer.namedo not create a global variable.Technical type :
set. Runtime :nodulz.Credentials and prerequisites
This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.
See the credentials guide if a remote source or execution target requires access.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
fieldsarray[]fields[].namestringfields[].valuestringmappedOnlybooleanfalseConfiguration help
mappedOnlyMapped fields only
fieldsVariables
Examples
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "fields": [] }Verification
Check that
amountis a number in the inspector andcustomeris an object. TogglemappedOnlyto observe preserved fields and added metadata. In the next node, select the field through mapping instead of assuming it is undervars. The complete tutorial uses this output in an IF.See also : Expressions and data, Executions, Node catalog.