Welcome to the Make community!
The “Create an archive” module is already an aggregator, so it does not make sense to have another aggregator before it.
Also, the output of the Search Files module does not output an ARRAY, so you do not need an Iterator module.
All you need to do is to map the “Source module” of the Archive to the Search Files module.
Setting the Correct Aggregator Source
You need to set the “Source Module” field of the aggregator to where the bundles are coming from. This is usually an iterator module, but can also be a search/list/repeater module, or even the trigger module!
Combining Bundles Using Aggregators
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?
You can also learn more about this in these Make Academy units:
Modules, scheduling and bundles
- Blueprints
- Different types of modules - search
- Different types of modules - action
- Introduction to triggers
- Scheduling your scenario
- Introduction to bundles
An introduction to aggregators
- Introducing Aggregators
- Numeric Aggregators in action
- Text Aggregators in action
Hope this helps! If you are still having trouble, please provide more details.
— @samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!
