Help Building a Leaner Google Docs → Airtable Mapper for Google Docs Tab IDs—Struggling with Multi-Nested Arrays, Collections & Bundles

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!