I’m currently using Knack and Make.com as my no-code stack in our company. I would like to move away from Knack for various reasons. I’ve tested different no-code platforms, and Glide is by far the best one I’ve tried. However, there is one caveat: “Updates”.
Each night, I have an automation in Make that updates all our customers’ products. Let’s say we have 15 customers, each with 10 products—15 x 10 = 150 updates per run, just for that workflow. I also have other workflows running as well.
I will exceed the 5,000 updates (Business plan) limit multiple times, which makes it very expensive for us to move to Glide.
Are there any good solutions for limiting the use of “Updates”? How do you optimize your workflows to reduce the number of consumed updates? I would really like to find a good solution so we can use Glide, but based on my current understanding of how Glide works, it would be a very costly solution for us.
There are multiple ways to reduce updates consumption. What would you want to do in these workflows ?
@MaximeBaker loop through each customer in the glide database > connect to external api and get a list of all their products with the qty > loop through each customers products in the glide databse and update the qty in the glide database with the qty grabbed from the external api
If there’s a way you can use Glide Big Tables for your products table, I would do it like this:
- Have a list of customer IDs, or any way you can identify those customers.
- Every day, query your external db using that list, so it returns a list for products related to all customers.
- Use Glide’s Stashing API to replace the Products table with the newly grabbed list of products. It will reduce your updates consume a whole lot.
1 Like
Sounds like an excellent idea 
But Big Tables is only for enterprise subscriptions, right?
It’s available on any newest plans I believe.
Can confirm, I created a new team and can add Big Tables on Free. However, you must be on at least Maker to use the Glide API via Make, I believe. On all plans higher than Maker, you can call the API anywhere.
