What is your goal?
My goal is to automatically assign incoming Facebook leads to my travel advisors using a round-robin system.
Each new travel request should be assigned to the next advisor in the list, and once the end of the list is reached, the assignment should start again from the first advisor.
I also want to ensure that only “travel requests” are distributed this way, while other types of leads (like advisor applications) follow a different path.
What is the problem & what have you tried?
I am receiving Facebook Lead Ads correctly in Make, but I am unable to properly route and assign the leads.
I want to:
identify the type of request (travel vs advisor application)
send only travel requests into a round-robin assignment system
However, I am experiencing issues with:
Router filters not consistently triggering for travel requests
Difficulty extracting the correct value from Facebook fields (they come as arrays or structured data)
No reliable way to rotate assignments between multiple advisors
As a result, travel leads are either:
not passing through the correct router path, or
not being assigned in a rotating sequence
What I have tried:
Used Router filters with conditions like:
contains(lower(Type_demande); “voyage”)
Tried extracting the value using:
get(map(field_data; values; name = “Type de demande”); 1)
Simplified the scenario by removing the router and sending all leads to email
Attempted to use a Set Variable module to clean and standardize the field value
Tested with Facebook Lead Ads testing tool (Run once + test leads)
Despite this, I still cannot:
reliably detect the correct lead type
implement a working round-robin assignment between advisors
Error messages or input/output bundles
There are no explicit error messages in Make. The scenario runs without errors.
However, the issue occurs in how the data is interpreted and routed:
I receive two types of values from Facebook Lead Ads:
Planifier_un_voyage_​
Devenir_conseiller(ère)_en_voyages_​
These values are coming from the form as structured data (arrays), for example:
field_data:
[
{
name: “Que souhaitez-vous ?”,
values: [“Planifier_un_voyage_​”]
}
]
Because of this structure, the Router filters do not always match correctly, even when the value appears correct.
What I observed:
The value is inside an array (values)
The text also includes special characters (emoji and underscores)
Filtering conditions sometimes fail, especially for Planifier_un_voyage_​, while the other option may pass correctly
As a result:
Leads are not consistently routed to the correct path
Travel requests are not reliably identified for assignment
Create public scenario page
Screenshots (scenario flow, module settings, errors)