Hi you all,
I’m fairly new to make. I am creating a scenario that triggers when a task is updated/moved into a new status in ClickUp. It then retrieves all tasks linked to that main task and aggregates their full details for use in a downstream module (e.g. PandaDoc). This is how I arranged it:
|
1. |
ClickUp - Watch Tasks: Triggers on task updates or creation. |
|
2. |
ClickUp - Get a Task: Retrieves full details of the triggered task. |
|
3. |
Iterator: Loops through the task’s linked_tasks. |
|
4. |
ClickUp - Get a Task: Fetches each linked task’s full data. |
|
5. |
Array Aggregator: Combines all linked task bundles into a single array for further processing (or at least this is the plan). |
I need to work with information from all three tasks, since the first task is the Project, the second the client and the third is their company. And in Pandadoc I will need all three.
Now there are two tasks (company and client) linked to the Get Project task 2 that’s why I am running an iterator in Step 7 and that’s why step 11 outputs two operations.
I then need the information from both of these operations in the PandaDoc module. So I planned to aggregate them with the Array Aggregator, but after hours of trying, I’m thinking, that I might need something else to process these Operations not Arrays, or my setup is wrong:
It looks like I’m only getting the first task’s data, as of now:
My question:
How can I turn the two operations from Step 11 into something usable in the next module (ideally as variables I can map in PandaDoc)? Do I need a different module instead of the Array Aggregator? Or is my setup flawed?
Any help is appreciated, happy to clarify if needed. Thanks a lot!
Hey there,
you always aggregate the module that is producing the extra bundles. In your case that is the Iterator module No 7.
1 Like
Thanks a lot for this lightning fast response!
It seems to work better, but I am still not able to grab both values in PandaDoc:
Output of the Aggregator looks like this:
What am I missing here?
You are mapping the first item of the array there, this is why you are getting only one item.
Sorry are there only two tasks in the Linked tasks field? And will there be only two tasks there?
And also, what info do you need from the tasks?
If its only ever going to be two linked tasks and you need to map multiple items from each of them → then I suggest replacing this flow with two get a task modules instead and just retrieve them directly. You will save an operation and be able to freely map whatever you want from each task.
Not sure I get your first questions correctly. There will be three tasks in total but only two linked. The main one from step 2 and the two liked ones shown here in the output, which I am trying to get in step 11.
As much info as possible, if that makes sense. If not, just the title, and custom fields.
So you would just have two get task modules in one row, or in a splitted row?
I think I tried something similar here, but not in one row:
Yeah you need iterator and aggregator if there will be either a large number of linked tasks or an unknown number of linked tasks, or if you need them inside an array for processing in a bundle.
If there is only ever two linked tasks and you need info from both of them, then just use the Get a Task module twice instead to retrieve each of the tasks.
All right thanks a lot, I’ll try tomorrow. Thanks a lot!
Hi there Stoyan, thanks for your help yesterday!
I tried to solve it now in one row. I did it by filtering the first bundle before the third task. Is this how you’d do it?
Anyway, it seems to do the job now, many thanks!
No no, ditch the iterator completely. You can use the order index of the two tasks to map them directly in the modules after.
4 Likes
Awesome, thanks a lot!! I had no idea it works like that. This is soo important to know!
2 Likes
