I’m trying to save on operations, but for some reason, this part of my flow keeps repeating exactly 6 times. There aren’t even 6 subtasks in the task I’m looking at, only 3.
1 Like
Hello @Adam_Bauer and welcome to the Make Community!
One of your module that comes before ClickUp is acting as an iterator and returning multiple bundles. All modules after that are running once for each bundle. In this case it’s 6 bundles.
We would need to see your entire scenario and hear from you how it’s supposed to work and we can advise on any changes.
Hope that makes sense and hope it helps!
1 Like
Welcome to the Make community!
Aggregators
Every result (item/record) from iterator/list/search/match modules will output a bundle. This can result in multiple bundles, which then trigger multiple operations in future modules (one operation per bundle). To “combine” multiple bundles into a single variable, you’ll need to use an aggregator of some sort.
Aggregators are modules that accumulate multiple bundles into one single bundle. An example of a commonly-used aggregator module is the Array aggregator module. The next popular aggregator is the Text Aggregator which is very flexible and can apply to many use-cases like building of JSON, CSV, HTML.
There are other types of aggregator modules, click the below links to find out more:
- Array aggregator
- Text aggregator
- Numeric aggregator
- Table aggregator
- JSON aggregator
- CSV aggregator
- Archive (ZIP) aggregator
- other app-specific aggregators
Array Aggregator – mapping multiple bundles into a complex field
The Array Aggregator module is very powerful because it allows you to build a complex array of collections for a later module’s field to map multiple items (collections) to it.
This is done using the “Target structure type” of an Array Aggregator module.
Here is an example:
As you can see, the “Map” toggle on complex fields are used when you have an array. You can easily build an array variable to map to a future module’s field, by using an Array Aggregator module and select the “Target Structure Type” as the future module’s field you have mapped the array into.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
Here is what I’m trying to accomplish with this step of the workflow:
Get a shared link on a folder in Google Drive, and then add that shared link to a custom field in the ClickUp task. The task I’m updating the second time is a subtask of a subtask.
It looks like the attached operation to list all custom fields is outputting 6 bundles for the 6 custom fields. I don’t believe this is needed when using the edit custom field operation. So I have removed that and we’ll see if it works again.
Thank you!
1 Like
Hey @Adam_Bauer
After list module, you need to deploy array aggregator and then process further.
Regards,
Msquare Automation - Gold Partner of Make
@Msquare_Automation
You’ll need the List All Accessible Custom Fields module if you don’t have enough information to update the custom field.
In this case you might be able to just add a filter and only allow the bundle to pass where Custom Field Name = Google Drive File. Hopefully that’s just one bundle and not all 6.