Building a Leaner Google Docs → Airtable Mapper for Google Docs Tab IDs

[Jake_Russell]

Use Case:
Every new project creates a Google Doc template (includes: 3 parent tabs → child tabs → nested “child 2” tabs) and creates 30 Airtable records, each holding a unique title in the Note 1 Title field.

Pain Point:
Our current Make scenario burns through 3,000+ operations to match and update those 30 records.

Current Solution:
We fire a webhook per record (recordId, note1Title, googleDocId), then use two iterators plus a filter to traverse the nested “child 2” arrays, find the matching title, extract its tabId, and push it back via the Update Airtable module.

Goal:
Identify a leaner strategy—flattening a hierarchy level, using direct lookups or batch processing, or another approach—to dramatically reduce operations while reliably mapping each note1Title to its Google Docs tabId.

Any help would be greatly appreciated!

[Stoyan_Vatov]

Hey Jake,

As I understand you get one webhook event, then get the document, then what are the two iterators iterating over? The the airtable updates a record 30 times per one document right?

[Jake_Russell]

Hi Stoyan,

From my understanding of it, Iterator 1 is needed to show the array of arrays. So, it’s iterating over the parent tabs, which then allows it to see all of the 1st child tabs (arrays) and subsequently 2nd child tabs (which have our matching tab title to Airtable’s Note1Title).

The data flows through to Update Airtable module when the filter matches the conditions. So, to match all of the 30 fields, it has to iterate many times to pass off one tabId at a time.

If I’m not explaining anything well enough, please let me know. Thank you!

[Stoyan_Vatov]

And how many bundles does the second iterator usually process?