Rename Keys

Node catalog Transformations

On this page

Rename keys while preserving values and other fields

Usage and specifics

Define mappings between source and destination keys. Check nested keys and collisions using a representative item before processing a batch.

Technical type : rename_keys. 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
`source`	`string`	`""`	-
`fields`	`array`	`[]`	-
`fields[].from`	`string`	-	-; min 1
`fields[].to`	`string`	-	-; min 1

Configuration help

source Source: Object or list of objects to rename. Empty: previous node data. Lists in items or body are recognized automatically. Output: items and count.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "source": "",
  "fields": []
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.