Date Field
What is a Date Field?
A Date Field is used when a workflow needs a date or date-time value.
When to use a Date Field?
Use a Date Field whenever the workflow expects:
a date,
a timestamp,
or a date-time value.
Good examples:
Use Case | Example |
|---|---|
Invoice Due Date | 2026-05-30 |
Subscription Expiry | 2027-01-01 |
Task Deadline | 2026-06-15 |
Scheduled Meeting | 2026-06-15T10:30:00Z |
Event Timestamp | 2026-08-10T18:45:00Z |
How to configure a Date Field?
Step 1 - Configure the Field
Fill in the field details:
Property | Value | Example |
|---|---|---|
Type | date | date |
Label | Field name (what the users see) | Due Date |
Key | API parameter name (what the API reads) | due_date |
Required | Makes the field mandatory | Yes / No |
Placeholder | Example date value shown inside the field | 2026-05-30 |
Help | Text displayed on hover for user guidance (Optional) | Enter or map the due date |
[
{
"key": "due_date",
"type": "date",
"label": "Due Date",
"help": "Enter or map the due date",
"required": true,
"placeholder": "2026-05-30"
}
]Additionally, attributes like defaultValue, visibilityCondition, dateFormat can be used as per need and requirement.
Step 2 - Save the Field
Click anywhere outside the field settings panel to automatically save the field.
