I’ve made a complex 2 scenarios in MAKE to have api call in tadabase, it has update records, create records, but the API calls/minute stops the scenario due to limitation, make can do all the way to 40 mins, but tadabase has limit per minute… How do you balance them together?
@TadaMan - Can you share in more detail what exactly your doing with the create and the update?
We might suggest a different approach with your make.com scenario that would not put you in an API limit issue.
Please feel free to reach out directly via DM or connect@rmelas.com
Adrian S. | EVP, Development • North America
RMELAS Technology Group
Tadabase Partner
If you complete an HTTP request module (not a Tadabase app module) the returned data will include the API call rate limit and remaining amount. Typically you will find this in Operation 15 and 16 of the returned data.
You’ll have to put a sleep module in periodically to allow a reset. You can dynamically apply this sleep module depending on the remaining limit, but that can get quite complex. The easiest way would be to just place a 60 second sleep and this will ensure that there is a full reset of the API call per minute.
I have applied bot…the dynamic wait and the static waiting…and by far the static waiting is the most effective. The only downside is that your scenario will take longer to fully execute.
The sleep module is a built-in module in make.com. You will not need to have any new subscription.