DateFormatter
Date Formatter – Date Format
Summary (SEO Meta Description):
The Date Formatter in WeHub converts input dates into different formats and timezones.
Configure input/output countries, timezones, and layouts to normalize or transform dates.
Overview
The Date Format action allows you to change the format, country, and timezone of input dates.
It supports a wide range of standard layouts (RFC, Unix, ISO, etc.) and global timezone identifiers, making it ideal for data normalization and cross-region workflows.
⚙️ Configuration Options
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the node (e.g., "Convert Appointment Date"). |
| Select Input Country | Enum | Country/region of the input date (e.g., Europe, US, Asia, Iran). |
| Select Input Timezone | Enum | Timezone of the input date (e.g., UTC, CET, PST). |
| Select Input Format | Enum | Layout of the input date. Supported: ANSIC, UnixDate, RubyDate, RFC822, RFC822Z, RFC850, RFC1123, RFC1123Z, RFC3339, RFC3339Nano, Kitchen, Stamp, StampMilli, StampMicro, StampNano, DateTime, DateOnly, TimeOnly. |
| Select Output Country | Enum | Country/region for the output date. |
| Select Output Timezone | Enum | Timezone for the output date. |
| Select Output Format | Enum | Layout of the output date (same supported list as input). |
💡 Example Use Cases
- Convert FHIR Appointment timestamps from
UTC→Europe/London. - Standardize dates from
RFC1123→ISO RFC3339for API compatibility. - Localize schedules to Iran/Tehran or US/PST for regional operations.
FAQ
Q: What happens if the input date is invalid?
A: The node fails with a parse error unless handled by workflow error management.
Q: Can I preserve milliseconds or nanoseconds?
A: Yes, use RFC3339Nano, StampMilli, StampMicro, or StampNano formats.
Q: Are daylight savings adjustments supported?
A: Yes, handled automatically based on selected timezone.
Keywords: WeHub Date Formatter, Date Format, timezone conversion, RFC3339, UTC, ISO 8601