Optimizing operation-usage of a scenario

Hello I’am quite discouraged right now.

I spent a lot of time building a Scenario that creates, updates or deletes contacts in Microsoft-Outlook(People) for every employee of my company. The central adress-List lives in Smartsuite.
The Scenaro is activated by a webhook and then checks for each Microsoft user if the contact is already there and what to do with it (create, update or delete). I did this quite cumbersome though. The branch you can see on the picture exists for every Microsoft user in my Company.
It is looking for an existing contact and, through the router, decides the action.
I am not very skilled in programming and I did not find a way to cycle through connections in a more elegant way. I think the Module does no even accept dynamic variables in the connection field.

Long Story short. I was quite happy but then I realized how operations work and that my Scenario eats up 30 Operations per execution. Thats nearly 9000 if I want to update my whole contact List. This sadly renders my Scenario too expensive and I’am quite lost.

Is there a better way to do this?

Welcome to the Make community!

Did you already limit the results to 1?

If yes, that’s already the most optimal setup you can have within Make.

Hope this helps! Let me know if there are any further questions or issues.

@samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

Hi, yes the Limit is in pace. Oh well at least what I did was the optimal way :smiling_face_with_tear: