Hi, everyone. I’m facing a situation and would like to know how you would handle it.
I don’t have access to the API because of my current plan.
I have an app where parents order meals for their children. The parents place the order, and the children simply pick up their meals by showing the order number.
The problem:
If Adalo goes down (Builder access and Apps access), the person in charge of delivering the food to the kids won’t be able to know what their parents ordered.
*Let’s say the Adalo outage happens right during the part of the day when these meals are being delivered.
-I know that with the API, each order could be fed into a spreadsheet via MAKE just after parents placed it which could then be checked manually to verify the order, but as I said, I don’t have access to the API.
¿How could they know what meals to deliver to the child, what would you do guys?
First - if Adalo goes down, Adalo API also goes down, so plan upgrade won’t help.
I assume that you have an access to Custom Actions. This means you can send information from Adalo to some external target. So I would think about a flow like:
parent creates the order in the app
app launches custom action and send order detail to Make scenario via webhook
Make scenario takes the payload and adds it to, say, Google Sheet
Hi, if you use back-up service/API it has the same problem, you can’t promise 100% reliability on any platform that runs online, unless you add some offline capability, as I know that’s not possible on Adalo, at least not easily. Adalo has outages very rarely, so I don’t think you should really worry yourself with that
If you would like to merge multiple values from multiple records in the same collection, that will be cumbersome.
But as an idea - you can send data when adding records one by one: when a parent orders a meal, you make a custom action call which sends details to Make.