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.

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!

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.

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! 🙏

I really need the variable "List name". Every list in our project space is a list. I need to add the List name to some task names and in a custom field. Feels like not to difficult?

Dropdowns Pleeeeeese!!

Very much needed! Importantly, there are many duplicate pieces of feedback in this Canny board about the different ways people need dynamic automations!

Yes, please. Use case: Now that "create a relationship" is an automations result option, it would be very helpful if that relationship could be based on a dynamic variable (e.g., trigger task ID). I use automations to create a task in list B when the due date for a task in list A arrives, and I would like to auto-link those two tasks and create a paternity record of sorts. There are hundreds of tasks in list A, so it is not practical to create individual autos using hardcoded values. My ideal auto in list B would look something like, "When task is created via automations, add relationship to trigger task".

I am wanting to use dynamic fields in an automation. Specifically, I want to set a custom field called Folder Name = the folder name the task is in automatically on task creation. I am doing this as a workaround because clickup will not let you show a tasks folder name as a column in views.