Use Case: I have a list of phone numbers that I need to send automated text reminders to. This list is created using several different tables and filters and requires calculated columns to get.
Context: I am rebuilding a Classic Glide App with the new Glide Platform and trying to keep within Glide Tables if possible. My previous app had this working via a Zapier Schedule automation and a lookup of a filtered cell in my Google Sheet.
Issue: Make/Zapier can’t PULL a joined list as they are not basic columns, nor can I PUSH the data from Glide via webhook because Glide does not have scheduled triggers.
Question: Does anyone have any workarounds on how I can achieve this without having to manually push a button in my Glide app at the same time every day? There seems like there has to be a solution to this that I am missing.
If you can wait it out a bit, and your flow to calculate the list of numbers isn’t too complex, I think Glide’s scheduled triggers would be helpful. They are working on it, just that I don’t have an ETA.
Can I assume that you also have data flowing in using Make/Zapier? The reason I ask, is that your predicament reminds me of attempting to convert an app into one that is compatible with Big Tables limitations. In that case, using basic columns where you would normally use a lookup can help.
If all the calculated columns required to build your list of phone numbers only depend on CRUD operations happening within your app, you could write the list to a basic column every time something changes. For example, if a user enters a phone number, when it’s saved, the list would be re-written.
No idea if this is feasible in your case! Just putting out an idea since using basic columns this way was a counter-intuitive workaround for making Big Tables work.
2 Likes
Thank you for your time and thought. Unfortunately I did already go down that path myself and it isn’t feasible for this specific use case. Too many ways that list can change and I don’t need to spend all those updates to maintain a constant list, just need to capture the filtered data at a set point in time.
A Glide scheduler would absolutely solve the dilemma! Honestly would an amazing update that would enable a lot of other improvements as well! No word on an ETA though? Curious if we’re talk weeks, months, or years.
Yeah, I have no words on an ETA for now, or on what plan would they offer it. I just have the information that they’re working on it though, and from what I’ve seen it would solve your problem.