I need some inspiration and feedback to see if my idea is possible!
Right now I’m building my own custom solution hosted on Azure - but it would be so much easier if I could make it happen on Make instead.
CASE:
I collect form leads from my website that I then send to my Make.com scenario in order to process the lead, add/modify/delete some data and distribute it to max 5 of my external partners by direct HTTP requests.
Finally I need to save the lead to a database and which partners it was sent to for statistics.
Important notes:
I will have more than 5 external partners, so I need to exit the loop when the lead has been sent to 5 partners successfully or the list of partners has been exhausted.
The partner can chose to either accept og decline the lead with a 200 or 500 response.
All partners will have different API endpoints and different data requirements.
I will need to keep track of leads sent to which partners and prioritize partners from least to most leads received.
I need to be able to query the database for leads sent for statistics.
This seems to me like a somewhat complex scenario!
How would the competent community of Make make this happen?
How quickly do you expect your partners to respond to your HTTP request?
Make has about a 40-second window in which it waits for a response.
For loops, Make doesn’t really have that but it’s come up a lot recently so you can find plenty of posts about it containing options to work around it.
High level, you could keep a list of your partners’ endpoints in a Data Store, Airtable, etc… then query that list when it’s time to submit them all.
I don’t know what the data payloads look like or even if they are the same, but you might be able to create sort of a template system and fill in the appropriate data for each HTTP request.
Make can submit those HTTP requests one at a time, but not all at once.
The partners will respond close to immediately to the requests… so I dont fear a timeout.
And yes, the data payloads will ALL be different from partner to partner endpoint. However, I’ll have all the necessary data from the form lead received by the webhook.
I figure I’ll need a specific data mapper for each partner endpoint, and some way to hook them together.
One HTTP request at a time is also required as I need to consider if the partner rejected or accepted the lead before moving on to the next partner.
This scenario require some level of abstractions and I’m not experienced enough with Make to figure out how to actually implement it…
I would suggest completing the Make Academy before jumping into building a complete scenario.
If you need specific assistance when you are building a scenario it’s easier to help you then.
Otherwise, you can also hire a professional by posting in the Professional Services category.
Here are some useful links and guides you can use to learn more on how to use the Make platform, apps, and app modules. I found these useful when I was learning Make, and hope they might benefit you too —
Perhaps something like this in your main scenario, but you’ll need an Enterprise Plan for scenario inputs to be near-instant (since we only have a 35-ish second window if we subtract overhead).
Starting with the router, it takes the 1st route and makes the first partner request.
If a yes (code 200), moves up to Tools module #2 which is sets some variables that you’ll need downstream.
If a no (code 500), moves down to Request Partner 2, then repeats the process until you get a yes.
Once one of them responds yes, the variables will be set.
Then, the flow goes back to the beginning router and resumes on 2nd route.
Tools Get Variables will get all the variables you’ve set from the first main route.
As you add partners, you’ll need to add more groups of these modules (HTTP, Router, Tools Set Variables). Over time, you might get to a point where you could parameterize the details you’d need for the HTTP requests.
Does that make sense? If not yet…like the others have said, once you get through a bit of training in Make this will all make much more sense.
