Our team uses Airtable to keep track of customer orders, and we’d like an automation that sends an email to the customer when our Airtable users make record edits that trigger certain events to happen (order placed, order confirmed, order out for delivery, order delivered, etc.). We want our emails to be HTML-formatted, so instaed of Airtable Automations, we are still using Zapier or Integromat, which trigger when the an order record enters a certain View. We are thus concerned about the Airtable API rate limit (5 requests per second) because we want to avoid a 429 error at all costs.
Our questions are:
-
Do services like Zapier and Integromat throttle Airtable API requests by default? If we were to say bulk-approve 100 or so orders on Airtable, will these services naturally throttle the emails to fit Airtable’s API rate limits as long as we are still within the Zap/Operation limits of Zapier/Integromat?
-
In the API documentation, the API team recommends using a “caching proxy.” What is a caching proxy and is it applicable in our situation? (I’m from the product side actually, so I’m not familiar with this concept).
-
I saw a post about Integromat’s Sleep tool being used to get around Webflow’s API limit (60/minute) – will Integromat’s Sleep Tool also work for Airtable’s API rate limit?
-
If we were to settle for Markdown-based emails, is there throttling on Airtable Automations by default? Or is there also a hard limit with risk of getting a 429 status code?
-
Having read about our use case, is there a “best-practice” way or clever workaround anyone can suggest to getting past the Airtable API rate limit?
