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.

It would be great if we have the ability to insert dynamic fields (custom or not) from a task to a doc related to it. (Dynamic Task Field Variables in ClickUp Docs)

Currently, ClickUp Docs do not support the dynamic insertion or automatic updating of task-related data (e.g., task name, due date, custom fields) within the document content. While tasks can be linked using the /task command, this only embeds a basic reference without pulling specific field values into the text. This requires manual copying and updating of task data, which is time-consuming and prone to errors, especially in projects where task details frequently change.

Requested Feature:

Add support for dynamic variables or placeholders in ClickUp Docs that automatically populate and update with values from the associated task’s fields. For example:

Users could insert placeholders like [TASK_NAME], [DUE_DATE], or [CUSTOM_FIELD_NAME] in a Doc.

These placeholders would pull real-time data from the task linked to the Doc (or a specified task).

Any updates to the task fields (e.g., a changed due date) would reflect instantly in the Doc without manual intervention.

Proposed Functionality:

In the Doc editor, provide a command (e.g., /variable or a dropdown) to insert dynamic fields from the associated task (e.g., name, status, due date, assignees, custom fields).

Allow users to define which task’s data to pull if multiple tasks are linked (defaulting to the Doc’s parent task).

Ensure the fields update automatically in the Doc whenever the task data changes, similar to how task links reflect status updates.

Optional: Support for formatting (e.g., [DUE_DATE:MM/DD/YYYY]) and inclusion in tables or text blocks.

It would be great if you could minus or add to a number field from an automation. Like a counter that triggers when you want it to. Thanks.

Zach I have a relationship between two lists (A & B). I want to have the information of this relationship in a third list (C). Rollup fields do not display relationships (and custom fields).

So my idea is to use an automation the following way:

When relationship from A to B (or B to A) is created, set relationship A to C. This does not work. I would need a dynamic field (or any other solution.

Yes!!! I would love to be able to create a subtask based on the parent task. Here is a loom of me trying to figure out how to do that for meetings. I have a subtask for each person that attends a meeting so that we can track time for each person separately and then the parent task(meeting) can see the total man hours spent in that meeting.

I want the due date to be based on the parent task this automation is triggered by.