Iterator + router + aggregator <- operations-effective design?

Hello Makers,

I’m trying to improve on the operations consumption of a scenario.

There’s an iterator and route with three different aggregator outcomes.

Despite the filters on each route, all aggregators are executed.

I’m wondering if a more efficient design is possible?

Thanks!

I believe aggregators always fire once per array processed by an iterator, even if no data comes out of the aggregator. based on the fact that after aggregators I very often use a filter to stop the scenario if the content of that aggregator is empty.

There are various operation optimization tricks, but its very much based on your specific data structure coming in.

Like in some cases you could place the filter and router before the iterator, and have multiple iterators instead (more modules but less operations)

1 Like

I assume this is in relation to the screenshot you posted. Could you please elaborate further? perhaps a wider screenshot?

Here’s an example of a usecase I’m trying to optimize (running every day):

  1. retrieve all users from Google Workspace Admin.
  2. Add row to a Google Sheet for every user.
    I’d like to optimize by avoiding adding rows for user that are already on that sheet. I thought I should add a “Get range values” module but not sure where to place it and how to filter by it.
    I tried this:

And this:


Obviously, it’s not working :slight_smile:
Any ideas?

Edit: Will circle back, briefly forgot that all google apps return collections that have to be aggregated,
rather than an array of collections.