Reducing #of operations updating Airtable

Hi all,

I’m running into a optimisation issue and I hope to get some ideas on how to improve my scenario.

Background:

I’m building a simple email automation for a charter rental company and everyday I need to pull all reservations (unfortunately the API of their booking system doesn’t allow to register a webhook for new reservations…), iteretarate through them and for each reservation call another API endpoint to fetch client details. After I fetch this, I need to update/create these records in Airtable.


blueprint (1).json (67.1 KB)

Problem:
There is no logic or option to only get new reservations, and it’s important to refresh the database daily as there are last minute and ad-hoc reservations which then need to be added to different email sequences.

Running this script daily consumes too much operations to be profitable so I’m looking for ways to optimise the consumption.

Ideas so far:

  1. Since the goal is to avoid iterations, it would be ideal to somehow filter out only the new reservations (not present in Airtable) and run the extra steps for those only (how?)
  2. Only fetch current and next months reservations (not all year).
  3. Instead of doing the iterations in Make, upload a JSON file to airtable and create the automation script in Airtable that iterates over the file and updates/creates records (seems like an overkill).

Any suggestions?

Without knowing what each module is doing, and what the output bundles of each module are like, it is difficult to advise.

If you need assistance, please use the Hire a Pro category, where you can receive private 1-to-1 assistance via video call/screenshare/private messaging/etc. This may help you get your issue resolved faster especially if it is urgent. It is important to post your request in the Hire a Pro category, as forum members are not allowed to advertise their services in other categories like here (even if it’s free/unpaid). Once you have posted in the Hire a Pro category, that will allow other members to assist you over other forms of communication, like screenshare.

Hope this helps! Let me know if there are any further questions or issues.

@samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

Appreciate the suggestions! Unfortunately, I can’t share the input/output of the nodes as it contains a lot of PI which I don’t want to expose.

Node 1: GET HTTP request to fetch all reservation detilas
Node 2: Parse the JSON
Node 3: Extract only the key values from the JSON (there is a lot of irrelevant data for each reservation so I extract key details like id, clientId, dateFrom, dateTo, commission, price etc.)
Node 4: Iterates through each reservation
Node 5: For each reservation make a GET request to fetch client details based on clientId
Node 6: Parse
Node 7: Extract only the key values from the JSON (name, email)

Hope this helps