I’m stuck at the 2nd part where I need to filter and check if it is a sub task.
Please can someone elaborate on these steps included in each of these 4 steps?
I’ll include the original post details here to save you following the link outside of this post:
Wim Jan 12 It’s actually very simple… in step 1 a webhook that picks up newly created tasks. Step 2: collect info from the task in question. Filter: if it is a subtask (with a parent id) then it may continue, otherwise not. Step 3: gather info from the parent task. Step 4: adjust the variable fields of the subtask with those of the task. The ids of the different fields can be obtained by adding, temporarily or not, the module list all accessible custom fields. If it is a fixed id you don’t actually need that module for the process.
the filter is placed between the second and third module and checks if the Parent variable exists → if it does then what you have is a sub task and you can use the value in the Parent variable to retrieve the parent task.
In step 4 you just map the corresponding custom fields from the parent to the subtask. They should have the exact same names and value types so this should be easy.
Many thanks @Stoyan_Vatov
Indeed at stage 2, if it has a parent, I want to proceed or otherwise stop the automation there.
My question is which value to input if true or false. See screenshot where I’m upto:
In the second module you map only the Task ID coming from the first module. You place the filter on the path after the second module and make it Parent exists.
That depends entirely on the custom fields you have in the parent task. When you open the module you should see the available ones listed and just match the names and map them.
Both the parent and the sub have a custom field who’s value needs to be a link to a task in a different list.
Since it is a link, it includes an array of objects like the name and the link.
To be clearer, I have a list of clients. Every client is a task. I include a link to the client in every case/task/toDo of that client. For that I have created a custom field called ‘Client’.
I keep getting an error saying “Array of objects expected in parameter 'custom_fields” and other errors.
I’m not sure about the syntax.
Also, in the sub-task, it didn’t fetch any custom field with the name client. I find that ClickUp only adds the field to the task if it has a value (i.e. in table view, I can see the “client” column blank at that line, so I can enter it but when viewing the task on its own, I can’t see the custom field with the name Client - this might be an issue in such automation).
