Ability to use more dynamic variables inside Automation actions
future
Александр Волков
Problem:
Automation does not work for us, because we need to populate properties relative to other properties in the task (not “hard-coded”).
From support:
Automations currently only support hardcoded values. Dynamic field values for automations is a great suggestion! I would recommend dropping by our feedback board and leaving any suggestions there!
Log In
Zach - ClickUp
Last updated on April 6, 2026
Hey everyone, I wanted to share the results from the little survey I sent out the other week!
Thank you, by the way, for responding to that. I think this does a nice job capturing what we should tackle next when we come back to this task. I will pin this comment to the feature request so all newcomers know the most desired updates.
Thanks!
Photo Viewer
View photos in a modal
Zach - ClickUp
Merged in a post:
Ability to add tag as an active field in automation
Michał Mrzygłocki
It is not possible to use "tag" as an active field which can be added in the automation similar as [Task name], [Assignee(s)] and custom fields as well.
We are using tags as project numbers and that works really well so we would like to keep it this way but also be able to use this data in automations
Photo Viewer
View photos in a modal
Zach - ClickUp
Merged in a post:
Use tag value to assign to custom fields
D
Dev VFV
I would like to extract tag value to use as value for my custom field. This would give us a ton of options when we try to bring data into ClickUp.
Zach - ClickUp
Merged in a post:
Enable Automations to Use Values from Custom Fields
G
Graham Flokstra
Currently, ClickUp automations only allow setting a custom field to a static value. I’m requesting the ability to dynamically set the value of one custom field based on the value of another custom field within the same task. This would allow for more powerful and flexible automations, especially in workflows involving calculations or field syncing.
For example, when a task’s status changes, I’d like to automatically copy the value from one custom field to another. This functionality would greatly enhance automation logic and reduce the need for manual update.
Zach - ClickUp
Merged in a post:
"Fields from Trigger" for all fields in Automation
Александр Волков
There is an option to populate StartDate ("date" type) with "Fields from Trigger", but we need such option for all types of fields (for ex: populating "Assignee" from another "User-type-field" will make it possible to use ClickUp as Workflow Management System)
Zach - ClickUp
Merged in a post:
Copy custom field value to other (custom) field in automations
Rob Geraedts
It would be valuable to be able to copy the contents of one (custom) field to another (custom) field, in an automation trigger.
Our immediate need is a situation where we want to copy the value of a "labels" type field, to another "labels" type field, on the trigger "existing task copies or move here".
We have a list will tasks, grouped by a "Release" custom labels field to store our release version. After release, all tasks are moved to another ("Closed") list.
Over time, we end up with a Release field that have 50 or more release numbers that will never be used again. I want to delete those values, but I can't , because then all release history for closed tasks will be gone as well.
A solution would be to create a second custom labels field. when I move a task to the Closed list, it could copy the "release" field value to the "release_closed" field. I could then safely delete "old" release field values in the main list.
Of course there is a "set custom field" action, but that can only set a value to a field, not copy another field's value to it.
J
Jame J Donovan
I do this sort of thing w Brain all the time. You could make an Agent that sweeps these fields either by schedule or a manual trigger.
Sarah Marsh
I agree with the importance of being able to dynamically link a custom relationship field. This is a use case that I wrote up for a similar ticket specific to automating assigning custom relationship fields dynamically:
This would be a valuable use case for my company. Currently, the only option for setting a custom relationship field in an automation is by hard coding the task to be linked. We want to develop an automation that will duplicate a task, and set a custom relationship to the task that triggered the automation.
We need to use a custom relationship, and not the built in relationship, because we want to have a rollup field that reads a custom field. As far as I can see, this is only possible using a relationship field that is tied to a particular list.
In the end, this would allow us to build a structure where high level tasks live in a top level space, and sub task items are duplicated into departmental spaces for the work to be completed. The automation would link the top level item to the work item in the departmental space. Then, URLs of final products can be posted in the departmental space, and rolled up into the top level space.
Zach - ClickUp
Last updated on April 6, 2026
Hey everyone, I wanted to share the results from the little survey I sent out the other week!
Thank you, by the way, for responding to that. I think this does a nice job capturing what we should tackle next when we come back to this task. I will pin this comment to the feature request so all newcomers know the most desired updates.
Thanks!
Photo Viewer
View photos in a modal
R
Ralph Stokes
For me I want to be able to use more variables from the trigger.
I have an automation set up for "Client" tasks in a CRM list that creates a project list when the client is won (i.e. on status change). I want to to use the name of the trigger in the list name - so I'm expecting a series of fields that we'd be able to enter anywhere in an action like {trigger name}, {trigger date}, {trigger custom_field}.
If these could be combined with a formula syntax for dates and numbers that would also work well - i.e {trigger date +3}.
For me dynamic variables inside automations simply means being able to reference any piece of data from the trigger, in actions.
Zach - ClickUp
Last updated on March 24, 2026
Hey everyone!
It's been a while since we've shipped the main asks here of dynamic people fields, date fields, and Formulas based on your feedback here. We know there's more to do, so we put together a quick survey to understand what we should tackle next.
This should take 30 seconds to fill out. Your answers will directly shape what we build next.
Thank you! 🙏
Nathan Boyer
Zach - ClickUp Dynamic dates are still not flexible enough. I want to automatically set my Expiration Date field to 6 months after my Calibration Date field. Dynamic dates are currently only implemented for the automation's Trigger Date; there is no way to set date fields based on math applied to other date fields.
Load More
→