Hi there,
I have been using “list all tasks” before “create a task” in order filter to see if a name is already in the database.
The problem is that it creates a new task for every task that passes the “check” - So I get 10+ new entries.
I was wondering how to check the list - then if the name doesn’t exist, add it once to clickup.
Thanks
Every result (item/record) from trigger/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.
You can find out more about the other types of aggregator modules here:
Question: Which is the best aggregator do you think you’ll need for your use-case?
Here is an example of how your scenario could look like:
This is just an example. Your final solution may or may not look like this depending on your requirements and actual data.
For more information, see “Mapping with arrays” in the Help Centre. You should also do the Make Academy, which also covers the use of Iterators & Aggregators.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
Hey Rob,
you can add the task name in a custom field and then use that to filter the tasks and see if it exists.
You can also have an internal clickup automation → when a tasks is created set that custom field to equal the task name.
Or like samliew suggested, aggregate the names coming form the List All Tasks module in an array and check if that array contains the name you are looking for.
Will try these, thank you!
