docs
EnglishChatigram website ↗Open Chatigram
date · utility

Date Picker

Parse and format dates from natural language input.

Plan availability #

Feature Free Starter Pro Enterprise
Active workflows 3 10 45 Unlimited

Allowances follow the published Chatigram pricing page. Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.

When to use this node #

Parse and format dates from natural language input.

Add Date Picker to a workflow branch using the node picker. Configure its fields in the inspector, then connect the next step.

Configure the fields #

Field What to enter
Date Input Natural language date input. Supports Gregorian and Persian calendars. Unicode numbers (۰-۹) automatically converted.
Gregorian formats:
• Single day: 25 (25th of current month/year)
• Ordinals: 1st, 2nd, 3rd, 4th, 15th, 31st
• Day names: Monday, mon, mo (this week)
• Next week: next Monday, next mo
• Keywords: now, today, tomorrow
• Day + Month: 11 Dec, 11dec, 11 december (current year)
• Day + Month + Year: 11 Dec 2026, 11dec2026, 11 december 2026
• Date formats: 25/11/2025, 11-25-2025, 2025.11.25
• ISO: 2024-11-22, 2024-11-22T08:00:00Z
Note: Check 'status' variable (valid/invalid) for workflow branching.
Time Zone IANA timezone name (NOT UTC+offset format). Affects 'now', 'today', and 'tomorrow' keywords. Examples: UTC, America/Toronto, Asia/Dubai, Europe/London, America/New_York
Example/default shown in the editor: UTC.
Calendar System Calendar system for input parsing. Options: gregorian (default), persian. Persian calendar (Jalali/Shamsi) is used in Iran and Afghanistan. Supports Persian dates like 1404/08/04 and Persian month names.
Choices: gregorian, persian.
Example/default shown in the editor: gregorian.
Locale Language for input parsing and output formatting. Options: en (English, default), fr (French), es (Spanish), ar (Arabic), fa (Persian), de (German), it (Italian), pt (Portuguese). Users can type dates in their language (e.g., '15 janvier', '15 enero', '15 Januar'). Output calendar is determined by the calendar field.
Choices: en, fr, es, ar, fa, de, it, pt.
Example/default shown in the editor: en.
Format Output date format. Type the format code shown before colon. Examples after colon show output.
Available formats:
• ISO or ISO8601: 2025-11-25T00:00:00.000Z (default, always Gregorian for Google Calendar)
• DD/MM/YYYY: 25/11/2025
• MM/DD/YYYY: 11/25/2025
• YYYY-MM-DD: 2025-11-25
• DD-MM-YYYY: 25-11-2025
• MM-DD-YYYY: 11-25-2025
• DD.MM.YYYY: 25.11.2025
• MM.DD.YYYY: 11.25.2025
• YYYY/MM/DD: 2025/11/25
• DD MMM YYYY: 25 Nov 2025
• DD MMMM YYYY: 25 November 2025
• MMMM DD, YYYY: November 25, 2025
• DDDD, MMMM DD, YYYY: Monday, November 25, 2025
• DD/MM/YY: 25/11/25
• MM/DD/YY: 11/25/25
Example/default shown in the editor: ISO.

Use the result #

Choose the output from the variable picker in a later step. Output names below identify the values supplied by this node; the picker inserts the correct reference for your node instance.

Output Meaning / label
result Formatted Date or Error
status valid/invalid

Connect the next step #

Connect the continuation shown on the canvas. Some nodes calculate their branches from the configured options. Read each branch label in the editor and connect the paths your workflow needs.

Test it in a workflow #

  1. Configure this node with a small, recognizable test input or a test resource.
  2. Check the variables from preceding steps and the connection selected in the inspector.
  3. Save the workflow. For event-driven flows, generate the actual event; use Run only for a Manual workflow.
  4. Open Workflow Activity and check the outcome before enabling wider use.

If something goes wrong #

  • Check empty variables, selected resource IDs, and any fields that appeared after resource selection.
  • Check the failed step in Workflow Activity before retrying. If the action may already have completed, inspect the destination first to avoid duplicates.
  • Follow the troubleshooting guide for a symptom-by-symptom checklist.

Catalog coverage #

This is the currently documented selection. Chatigram continues to add nodes, triggers, App Connections, and integrations. Use each page’s review date and the current application selectors to check what is available now; this catalog is not a fixed limit on future features.

Keep building.Need help with this? Explore troubleshooting ↗

Find an answer. Try “welcome workflow”, “database”, or “Telegram”.