Dynamic fields for Automations
Александр Волков
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
Hey everyone!
I wanted to share an update on our roadmap so you have a better idea of what's coming up next/in progress:
- Dynamic PEOPLE fields Almost done here (a lot of this is live already!)
- Dynamic DATE fields This has been prioritized and we are starting work soon
- Formulas in Automations Prioritized as well but not started
We try not to plan too far into the future to avoid taking on too much. So, this task will be after those three but not certain if it will be #4 for example.
I hope this clarity is helpful!
Specifically talking about this feature request, what would help me a ton is understanding what "Dynamic fields" outside of the ones I mentioned above are most needed by you.
Thanks 🙏
A
Alejandra Battaglia
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.
M
Mark Teague
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.
E
Elias Höfer
Zach I have a relationship between to 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.
Willard Moore
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.
Luci N.
Merged in a post:
Copying Custom Field Value While Running "Task Creation" Automation.
S
Shubham Bansal
I am using a "Create Task" when "Status Change" automation.
This gives an option to select which Custom Filed are to be copied while creating a new task.
Oddly enough, this works only for Task Name, and Task Description and Text Format Customer Fields.
For the above, it copies the task specific values, but for any other types of custom field formats like date, phone number, it only gives an option to insert a Static Field.
Roger Spalding
Zach I think what is missing is: it needs to copy a custom field filled like money to other List or even use it as a variable field in a comment... for exemple
Natalie Williams
Date published fields also don't function correctly. If running an automation to update a date field on another task from an existing date only the date is set the time is NOT set. So if you have times then you need to manually update those, which defeats the purpose of the automation.
E
Evelien Van den Berg
A dynamic field that would help me is the ability to dynamically select the task that triggered it and assign it as a linked task.
For example on task 1 a custom field gets a value of A, automation triggers and creates a new task, task 2, in a different list. Task 2 then has task 1 as a linked task.
What also would be helpful is to link a document to the task using the automation.
Avraham Jay
I don't understand why this isn't fixed, it's been 4 years since this was created.
Jay DiPietro
Zach The new people dynamic field is GREAT. However, it would be incredibly helpful to reference people in a custom field in a comment.
Example: We have a piece of content being developed and managed as a task. The content creator is the assignee. We also have a people custom field called "Approver" with another person assigned.
I'd like to be able to have an automation where when the due date arrives, if status is not approved, rejected, or closed, a comment is generated with an @ reference to the approver in that custom field so they are aware they need to get on top of it.
Load More
→