Use formula fields as automation triggers (including TODAY() and date-returning formulas)
Jonas Jacobs
Make it possible to use a defined formula as input for an automation. This as use case to set an SLA with escalation on the elapsed time.
Log In

Zach - ClickUp
Merged in a post:
Function field as a trigger for an automation
S
Stefano Lazzeretti
It would be very useful and important for function fields to work as triggers for automations. They currently don't work.
Thank you.

Zach - ClickUp
Merged in a post:
Automation trigger according to function result (especially TODAY())
H
Hadrien Maire
I implemented a simple function that calculates the difference between a date and the function TODAY().
The automation should trigger everytime this calculation is updated, hence everyday, although it does not.
It would be nice if automations could be compatible with certain functions to allow more flexibility on trigger conditions.

Zach - ClickUp
Merged in a post:
Utilize a Formula Field that includes the TODAY function as an Automation Trigger
Kathleen Heitzinger, RN
I would like to use this to create a formula field that tracks how many days have passed since the task's start date. I want to be able to use automations to create checklists that will populate when the task has reached different intervals.
For example, I would like to trigger a checklist for specific paperwork that needs to be done when any task in the space has reached 30 days after its start date.
Caroline Ginty
Merged in a post:
Allow triggers based on value of custom formula fields
Abby Fuller
I track items based on age in days. I have one formula field, "Age," that returns a numeric value of days-old based on another custom date field, "purchase date." So if "Purchase Date" is 3/24/26 and today is 04/17/26, the Age field's value is 34. Task statuses are based on age range; 0-89 days, 90-119 days, 120-199 days, etc. I want to run automations to change the status based on age value, then send a direct message when a task reaches a milestone date. Since automations cannot be triggered based on fields that are populated by formula, I am having to create new date fields so that I know the milestone dates, then create date fields and manually populate each of those date fields, then trigger the automations based on those dates. Even if it were possible to simply type the dates in and move on, this would be an excruciating process, but it takes quite a long time to populate all of these fields manually for 300+ tasks. The simplest option would be to allow automations to trigger based on the value of fields that contain formulae like DAYS, TODAY, or even allow for triggers like {Purchase Date}+90. Being able to set triggers based on values, regardless of field type, would be immensely helpful.

Zach - ClickUp
Hey Stefano! Are you asking for formula fields to be the triggers?
S
Stefano Lazzeretti
Zach - ClickUp
Yes, that's right.
Currently, custom fields can be triggers but not “formula” custom fields.
Custom fields of type 'formula' cannot even be filtered.
It would be very useful to have these 2 functionalities for 'formula' type custom fields
Thank you.
Caroline Ginty
Merged in a post:
"Now" Variable for Formula fields and the ability for "Today" Variable to Trigger Automations
Gergely Végh
Hi, It would be very usefull to have a "Now" variable in formula fields for automations , or the "Today" variable to be fixed so it could trigger automations, cause right now we have the "Today" variable but its of no use since it cant trigger automations.
It would be very usefull.
Ray Nino Aranas
I have the same concern.
When using a manual trigger based on a Date Type Custom Field set to "Today," it works correctly on the same day. However, on the following days, the trigger shifts based on the originally set date.
For example, if the trigger is set to "Today" on March 2, 2025, by the next day, it changes to "Yesterday."
Is there a way to keep the trigger fixed to "Today" at all times? If users need a specific date-based trigger, they can already utilize calendar dates instead.
Benedek Kiss
Yes, it would be very usefull. :)
Caroline Ginty
Thanks Jonas Jacobs! Would you be looking for a formula that uses existing dates from the task, e.g., "5 days after the due date" or "10 days after date created"? Or more complicated formulas?
Bilal Awan
Caroline Ginty: I believe a starting point would be great to use the existing dates, and then continue enhancing on the feature.
Jonas Jacobs
Caroline Ginty: Indeed we can start with this to accomodate the SLA feature.