No one really knows everything about scripting; you’re not alone. :winking_face:
I have some thoughts, but I’d like to be sure that “GS” is “Google G-Suite”.
To be clear - you have adequately met this requirement with Zapier, right? If so, are you simply looking for a more unified approach that doesn’t require Zapier?
Yes, it is possible for a single script process in “GS” to integrate with any of multiple different G-Suite accounts and multiple different Airtable bases and tables. To achieve this requires some security details, but they are mot overwhelming.
Observations
- As you make clear, Zapier recipes cannot dynamically expand if they are gated to specific customers. Google Apps Script (if designed well) are able to scale dynamically. Script actions (in Airtable can dynamically scale as well - again, if well-designed).
- Multiple views per status could be simplified - i.e., a single script automation looking for specific status field changes could dynamically determine the nature of the automated update without forcing records through a collection of views and then on to Zapier. Automated system tend to work better when there are fewer moving parts.
- The timing and control of an Zap is often difficult and tedious to develop. Furthermore, when multipole Zaps are needed, they often race ahead or lag behind creating additional timing challenges when there are process dependencies. Ideally, you want the automation process to have a single mind of its own.
- Automations seem to be far more successful if they are accurately diagramed in the requirements phase of the project. The example shown below is a good example.
There’s no restriction - it’s a free market and Airtable encourages users to find good help. And while most of the members are here to simply help and guide Airtable users, many - like me - are also consultants. My consulting is primarily in Google Apps Script but I also work in Airtable scripts, AI platforms, and a number of real-time networks and APIs.
