Zach That's exactly what I need. Nothing missing. Initial design looks fine.

Do you have a ship ETA?

Zach looks good mate. How would we "lookup" the correct task based on data from the triggering task? For example I have a list that receives customer feedback (tasks created via an API). On that triggering task, there is a custom field called 'customer UUID'. We have a separate CRM list that also stores this UUID. We'd like this automation to find the correct User in the CRM list via this UUID and make that relationship on that triggering feedback task.

Zach good evening! ,

Perfect, that's exactly what we're looking for as a basis for automation.

I would like to add some important technical considerations so that, at the time of constructing the solution design, possible evolutions are already foreseen:

In addition to creating the new task or subtask with the link of the parent task (trigger), which remains the priority in this first phase, it would be of great value to provide optional logic for automated linking with existing tasks from customized fields.

Examples:

-Link (relationship link) the new task to an existing one that has a custom “X” field with the same value as a field from the source task (trigger).

-Or link based on a custom “Y” field that contains a fixed value or specific ID.

To be more clear: as an example, I want this new task to be linked, in addition to the parent task (trigger), to all the tasks or subtasks in the XXX list that contain the same CNPJ as the source task. This CNPJ may be present in a customized field or in the title of the task, and can be identified both by exact correspondence and by partial content (contains or is equal to).

The first logic (for a common field between tasks) is more strategic, dynamic, and flexible. The second (hardcoded) option is more limited and less recommended in the long term.

It is essential that we can define how the relationship of the new task/subtask with the original or linked task will be displayed, using the same options as in the native ClickUp relationships tab:

1-Dependency

2-Task on Hold

3-Blocking

This maintains the standardization and logic of the system. Customization should allow you to choose which type of link will be established during automated creation.

I am available to detail each point, if necessary. Thank you for your attention and support in building this improvement!

Guillermo Sisterna

Zach good evening! ,

In addition to the previous text..

In our current environment, we use personalized relationships between tasks from different lists, where each list represents a distinct process. The new customization must preserve and enable the use of these custom dependencies, including cross-referencing between lists.

This functionality is essential to our operational flow. (As an example, I'm attaching a print.)

It would also be interesting to provide for the possibility of automatically attaching or referencing relevant documents to the created task, maintaining the traceability of the information from the initial trigger.

I am available to detail each point, if necessary. Thank you for your attention and support in building this improvement!

Guillermo Sisterna

Zach Agreed with other posters that some sort of smart lookup to the relationship via custom field or something is super important. For example for our use case, we have a list of Accounts. Then we have a list of Orders. If the Order can be linked to the Account via Relationship via Automation, that would be awesome. But it will be different accounts and different orders, so there will need to be something that tells the automation WHICH task to relate to the one being adjusted.

Also, alongside automations, it would also be great if there was a way for Relationships to carry over when duplicating a task. This feature currently does not work at all even though listed as an option when duplicating. So if that can be added into this feature improvement.

Zach Thanks for preview! Exactly what we need! I agree about second use-case, that there must be good way to lookup tasks for linking (as you mention tasks, not task). However I really hope that because of so much additional needs in second use case wont stop delivery of whole feature, because your first use-case could be used already, and we are really waiting for it, because currently doing this manually.

p.s. infact about smart linking we had this insane requirement to get a task from task link, where the link was named with unique name, if the task lookup could also have this kind of lookup, not only by some custom field value, I think you would cover almost all possible cases.

Zach This looks really good! What is the ETA of this feature?

I also want to emphasize the need of a proper possibility to dynamically select the tasks for the relationship.

In my case I'd mostly need a way to add the triggering task as one side and the newly created (sub-)task as the other side of the relationship. But sometimes it's also a static, pre-defined task that needs to be used.

Zach Hi Zach - Thanks for your hard work. I've read trough the other comments and i think it's great that we have some type lookup field that is dynamic against custom fields. This since we want to tie different new tasks to specific projects in other lists - so that we can understand what project this new task associates to

Zach Hey Zach! What's needed is smart linking - For example:

^This is a very common way of working when Developing. What's

Zach So cool, I would need this fast. Also, that I can use relations, so tasks in forms.

Zach this will work great for us! My only question is whether we can set custom task fields this way too or just those shown in the video. Those shown in the video alone is enough to get us going, so just curious for now, not an absolute need today!

Scott Henning Hi! Looks good! Will this include list relationships? I'm looking to automate the creation of a task in one list with a link to another list.

yes, we’ve been eagerly anticipating the ability to link a newly created task to/from a triggered task. And, it would be incredibly useful if we could also add a list of tasks in the form to link to (similar to creating a drop-down list to select from as a relation/link list elsewhere).

Zach Looks really excited. For my purposes I was hoping to have the ability for the automation to link multiple "create subtasks" in one automation. For example I have an automation set up for when a Heavy/Medium task is requested to add subtask 1 subtask 2 and subtask 3. Would be nice to have an automation to link these so that subtask 2 and subtask 3 are automatically marked as "blocked" by subtask 1.

Zach , thanks! The first option you demonstrated looks great. It’s imperative that it also works when duplicating tasks. Are you planning to include that as well? Since it’s not possible to inherit Custom Field values when creating subtasks or tasks via automation (also a feature request), duplicating the task is the way to go. But in that case, you’d need to maintain a link between the duplicate and the original. Thanks for your response.

Zach Excellent news – this crucial feature has been among the most sorely needed in my 4 years of building CU autos for my company. Can't wait to get my hands on this.

Thank you all for the feedback, I've compiled the asks that weren't present in the demo and will take it back to the team.

I think we will still go ahead and release what I showed once it's polished, but there is certainly room for growing this feature to be more helpful.

Zach

It looks good. Ready to ship.

I think you will get better feedback after it ships and users start using it. Then you will get feedback on its limitations and how to improve it.

Zach - looks great to me!

Zach That is so good, but I have another important case I hope you can cover it in this feature, so I suggest that when a status changes (or any other trigger action), then I want to get the task that is connected (by relationship) with the current task (that triggered the automation) and archive it, delete it, change It's status, or any other actions..., that would be very very helpful