Hi ​@natpointme 

For us to have more info, elaborate about the logic for the guard rails you are trying to implement in the round robin assignments based on the capacity and availability.

Best to outline specific examples for us to understand the inputs and expected outputs.

Also, post screenshots showing how your Zap steps are configured in EDIT mode with the field mappings visible.

so specific agents are available on a week to week basis — of these available agents, they also each have individual capacity (i.e. joe can only take 3 deals at a time, alex can only take 6). so it would need to be that the workflow would assess it like this: 

if joe is available AND has less than 3 deals, assign

if alex is available AND has less than 6 deals, assign 

if sue is unavailable, do not assign 

​@natpointme 

In the Airtable Find Record Zap step action, you can limit the data to a View.

In Airtable, configure a View with Filter conditions.

e.g. Filter: Availability = Available AND Deals < Capacity

Plus, you’ll also want to set a Sort so that Reps with the lowest # of Current Deals are at the top, thus chosen as the record when the Zap Runs.

You’ll also need to add these Zap steps:

• Formatter > Numbers > Perform Math Operation (Add)
  • Deals # + 1
• Airtable - Update Record
  • Used to update the Deal # field value with the value from the previous step

Can you clarify this step? 

• Formatter > Numbers > Perform Math Operation (Add)
  • Deals # + 1

Struggling to see how to input that here 

Hi ​@natpointme,

Just jumping in to see if I can assist!

We’ve got a Community post all about setting up a round-robin in a Zap — feel free to check it out and see if it helps:

Hopefully, this helps!