Date Transformer

Overview

The Date Transformation node converts, reformats, and shifts date/time values in a workflow. It takes a date input from a previous node or a literal value, applies an operation (such as adding days or changing timezone), and outputs a formatted string that downstream nodes can reference.

A single Date Transformation node can contain multiple transforms, each producing its own output attribute.

Requirements:

An input date value must be provided — either a literal value or a reference to a previous node's output.
An output format and output timezone must be set.
The output attribute name must be unique within the node.

Choosing an Input

When configuring a transform, select where the date value comes from:

A reference to an upstream node — use the output of a previous workflow step (e.g., a form submission timestamp, a CRM record date field, or another Date Transformation node's output).
A literal value — type a date string directly into the input field.

Input Types

Type	Behavior
Date / Datetime	Treated as a date object. Parsed automatically if a strict format isn't provided.
String	Treated as a plain string. An incoming date format and input timezone are required.
Auto (empty)	Type is inferred. ISO datetime strings and Date objects are treated as dates; everything else is treated as a string.

When using String as the input type, both the incoming date format and input timezone are required. Without them, the node cannot parse the value.

Operations

Each transform applies one operation to the parsed date:

Operation	Description
Convert Format	Change the timezone and/or format only — no day arithmetic is applied.
Add Calendar Days	Add a specified number of calendar days (including weekends).
Subtract Calendar Days	Subtract a specified number of calendar days (including weekends).
Add Business Days	Add a specified number of weekdays (Monday–Friday only).
Subtract Business Days	Subtract a specified number of weekdays (Monday–Friday only).

For arithmetic operations, the days value must be a whole number between 0 and 3,650 (approximately 10 years). For Convert Format, the days value must be 0 or left empty.

Output Format

Every transform requires an outgoing date format and an output timezone. The format uses moment.js tokens.

Common tokens:

Token	Meaning	Example
`YYYY`	4-digit year	2026
`MM`	2-digit month	03
`DD`	2-digit day	20
`HH`	24-hour hour	14
`hh`	12-hour hour	02
`mm`	Minute	30
`ss`	Second	45
`A`	AM / PM	PM
`Z`	Timezone offset	+05:30

For example, YYYY-MM-DD hh:mm A produces 2026-03-20 10:30 AM.

See the moment.js format documentation for the full token list.

Timezone Handling

Timezones use IANA identifiers (e.g., America/New_York, Europe/London, Asia/Tokyo, UTC).

Input timezone — specifies the timezone of the incoming value. Required when the input type is String; optional for Date/Datetime inputs (the node can infer it from the value).
Output timezone — the timezone the result is converted to before formatting. Always required.

Business Day Logic

When using Add Business Days or Subtract Business Days, only weekdays (Monday–Friday) are counted.

If the input date falls on a weekend, it is first moved to the nearest weekday in the direction of the operation before counting begins.
Add Business Days with 0 days on a Saturday or Sunday moves the date forward to the next Monday.
Subtract Business Days with 0 days on a Saturday or Sunday moves the date back to the previous Friday.
If the input date is already a weekday and days is 0, the date is returned unchanged.

Using Multiple Transforms

A single Date Transformation node can run multiple transforms in sequence. Each transform:

Has its own input, operation, format, and timezone settings.
Writes to its own output attribute name.
Runs independently — if one transform fails, it outputs null but does not stop other transforms from executing.

Output attribute names support dot-notation for nested paths (e.g., dates.followUp).

Two transforms in the same node cannot write to the same output attribute name or to conflicting paths.

Output Attribute Naming Rules

The output attribute name is the key downstream nodes use to reference the result.

It must:

Start with a letter or underscore.
Contain only letters, numbers, underscores, and dots (for nested paths).

Reserved names (not allowed): _logs, retryCount, error, executionStartedAt, executionFinishedAt, workflowIntegrationId, result

Error Handling

Scenario	What happens
Input is `null`, `undefined`, or cannot be parsed	The transform outputs `null` and the next transform continues.
Input type is String but no incoming format / timezone is set	The node throws a validation error before any transforms run.
Output attribute name is invalid or conflicts with another transform	The node throws a validation error before any transforms run.
All configuration is valid but a single transform fails	That transform outputs `null`; other transforms are unaffected.

Examples

Convert a timestamp to US Eastern time

Set the input to a previous node's timestamp field, choose Convert Format, set the output format to YYYY-MM-DD hh:mm A, and set the output timezone to America/New_York.

Result: 2026-03-20 10:30 AM

Add 5 business days to a date

Set the input to a date string like 03/20/2026 09:00, choose Add Business Days, set days to 5, provide the incoming format as MM/DD/YYYY HH:mm and input timezone as America/Los_Angeles, then set the output format and timezone.

Result: 2026-03-27 (weekends are skipped)

Run multiple transforms in one node

Combine operations in a single node — for example, convert a timestamp to UTC, calculate a follow-up date 30 days out, and format the date for a different region. Each transform writes to a different output attribute.