Date & Time

Node catalog Transformations

On this page

Manipulate date and time values

Usage and specifics

Choose the operation, input, format or offset. amount and unit describe the offset; distinguish seconds, minutes and hours.

Technical type : date_time. 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
`operation`	`enum`	`"format"`	`format`, `add`, `subtract`, `parse`
`input`	`string`	`"{{input}}"`	-
`format`	`string`	`"YYYY-MM-DD HH:mm:ss"`	-
`amount`	`number`	`1`	-
`unit`	`enum`	`"hours"`	`seconds`, `minutes`, `hours`, `days`

Initial configuration

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

json

{
  "operation": "format",
  "input": "{{input}}",
  "format": "YYYY-MM-DD HH:mm:ss",
  "amount": 1,
  "unit": "hours"
}

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.