I’ve seen the most complicated workarounds to do a round-robin in your scenario in Make.com, but it’s actually really easy.
You only need a module, a magic formula, and a router.
Let me show you how it works.
Table of Contents
Let’s dive in!
What is a round-robin?
A round-robin is a method for evenly distributing tasks or choices by cycling through a list in order, so everyone or everything gets a turn in a fair and systematic way.
For example, if you have a team of three, each team member gets assigned a task one after another until everyone has had a turn.
- Task #1 → Max
- Task #2 → Emmah
- Task #3 → Joe
- Task #4 → Max
- Task #5 → Emmah
- etc.
In a scenario it’s especially helpful to evenly distribute between routes in a router.
Implementation of round-robin
Step #1: increment function
First, add the tool Increment Function to your scenario.
The first time the scenario runs it will return a value of 1, and will then add 1 to the number every time the scenario runs.
So the fifth scenario execution the value 5
, and the nine hundred twenty-eighth scenario execution it will be 928
.

Step #2: magic formula
We’re going to use a formula to calculate and evenly distribute between your options.
Let’s say we have 3 options, what we want is this;
- Execution #1 goes to option #1
- Execution #2 goes to option #2
- Execution #3 goes to option #3
- Execution #4 goes back to option #1
- Execution #5 goes to option #2
- etc.
To do just that, we are going to use the mod
operator with a simply formula;
(628+1)mod3
= 1
Let me explain;
628
is the number from our increment function, this will increase by 1 every scenario execution.1
increases the number from the increment function by 1 so we select the next option.%
calculates the remainder after diving it by the amount of options.3
the amount of options
But you honestly don’t need to understand the calculation, I also find this modulo very confusing, haha.
Just change the number 3
by the amount of options you want, and the first number by the item from the increment function module.
(1. i+1)mod3
= 0, 1 or 2
This formula will now automatically return 0
, 1
or 2
every time the scenario runs.
If you want for example 5 options, you would use this;
(1. i+1)mod5
= 0, 1, 2, 3 or 4
See? We changed the last number to 5
and there are now 5 options.
Pssst. Want my best tips for Make.com? Get the cheat sheet 😄📩
Psst. Want to get the most out of Make.com? Consider my in-depth course 😄
Psst. Want some 1:1 help with your project? Book a coaching call with me 😄
Step #3: add router with filters
Now that you know the magic formula, let’s see how we can use it inside our Make.com scenario.
First, create a router with the amount of routes equal to your amount of options.
I want 3 options, so I created 3 routes:

And then click on the dotted line to create a filter with our magic formula for the round-robin:

Do the same for the other routes;
- Round-robin option #1 = equal to 0
- Round-robin option #2 = equal to 1
- Round-robin option #3 = equal to 2
And that’s it!
Every time the scenario executes, it will follow the next route in the router 🙂

Import: want this scenario? Import this blueprint to Make.com 🙂
Import: want to import this scenario? Become a free member 🙂
Over to you
Hope it’s helpful!
Any questions? Let me know in the comments below!
Oh man, this is amazing. I was waay overthinking this. Thanks!!
Happy to hear it’s helpful! 🤗
Nice! I think I get it but the modulo part still kinda tricky haha. Thx!
Haha yes, I have to say when I got started with this I also found the modulo a bit confusing.
Love the clear steps outlined!
Thanks!
Wait, can u explain more about the mod operator? I dont get how it works exactly.
The mod operator is just a way to make numbers loop. In
(i+1) % 3
, thei+1
is a number that keeps going up, and% 3
makes it cycle between 0, 1, and 2. So ifi
is 7, adding 1 makes 8, and dividing 8 by 3 leaves a remainder of 2. That’s how it picks the next option. Just swap out the3
for however many options you have, and it’ll loop through them over and over.Oh wow, I actually tried this before but got stuck on the formula bit, lol. Cheers!
Haha, hope you got it to work now Tyler!
Wow, this is super helpful! Been struggling with this, thx for breaking it down!
You’re welcome! 😄
Could you clarify how the increment function handles resets? What happens if the scenario stops?
Great question! Whether it resets depends on your setting: ‘after one cycle,’ ‘after one scenario run,’ or ‘never.’ If you choose ‘never,’ it won’t reset, even if the scenario stops due to an error or something similar.
Are you sure this method works reliably for larger scenarios? The explanation feels a bit oversimplfied.
Yes, the size of the scenario does not influence the effectiveness of this round-robin 🙃
Hi Max, nice explanation but still a bit puzzled how the ‘magic formula’ really ensures fair distribution over long run? Can it skew over time?
Hey Jenny! It distributes it 100% fair by going to the next route every time the scenario runs.
It works by using the increment function, which calculates the amount of times the scenario ran, and then with the formula we use the modulo operator to calculate the remainder of the formula, which will always be the next number because the increment function was one higher 🙂
Hope that makes sense!