Automations often need dates that depend on when something happens, for example "due 3 days after the task becomes high priority". Instead of a fixed date, you can use a date that’s worked out each time the automation runs.
You can use these dates in the Check if and Then steps of an automation, anywhere you’d pick a date.
The Date Options
When you pick a date in an automation, you can choose:
Dynamic date: a number of days, weeks, months, or years before or after the trigger. Turn on Skip weekends to count only Monday to Friday.
Relative date: another date of the same item, for example an invoice’s due date.
Interval: a period such as This week, Next month, or End of next week.
Fixed date: a specific day from the calendar.
📌 Interval isn’t available in every action.
In the "Check If" Step
Use these dates to make conditions depend on time. For example, check whether an invoice’s Sent date is within 15 days after the trigger:
Skip weekends in the count:
Compare two dates of the same item, for example whether the Sent date is the same as the due date:
Or check against a specific day:
In the "Then" Step
Use the same options to set dates in actions. For example, set a task’s due date to 3 days after the trigger:
Skip weekends in the count:
Set a date to match another date of the same item, such as the due date to the start date:
Or set a specific day:
Example
When: a task is updated.
Check if: its priority changed to High.
Then: set its due date to 3 days after the trigger.
High-priority tasks then always get a due date that gives the team three days.
👉 For the triggers you can start an automation from, see Setting Up the "When" Step in Automations.









