![]() ![]() Ideally, you want the automation process to have a single mind of its own. ![]() Furthermore, when multipole Zaps are needed, they often race ahead or lag behind creating additional timing challenges when there are process dependencies. The timing and control of an Zap is often difficult and tedious to develop.Automated system tend to work better when there are fewer moving parts. 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.Script actions (in Airtable can dynamically scale as well - again, if well-designed). Google Apps Script (if designed well) are able to scale dynamically. As you make clear, Zapier recipes cannot dynamically expand if they are gated to specific customers.To achieve this requires some security details, but they are mot overwhelming. 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. I am looking for a more efficient way to script from MY GS to customer GS = is it possible for a script to SEARCH multiple GS’s at once? *one step further I am looking for a more efficient way to script from MY GS to customer GS = is it possible for a script to SEARCH multiple GS’s at once?Īny insight/advise/guidance/“work done for me” is greatly appreciated!ĭon’t know if we are allowed to seek out professional help in these Threads, but I do need help building scripts/integrations *scripting!!! when the AT record is updated (only looking at few selected Fields) then the data is push/pull to MY GS. *using ZAP (row=updated - seeing all columns) to then push data from MY GS to customers GS (which *changes weekly :frowning: ) - so simply copy the ZAP and change the parameters to match their new sheet every Friday. ie: status change, date, new/old kiosk serial#, contractor. these are status update views (one for each status) that only pull certain Fields into GS from the ZAP. *Multiple views in AT (new to view = Zap specific fields to GS). ![]() Thank you to those who have done so! I have additional steps that ZAP from GS to other GS after the data transfer, so using one of them that I found was over triggering my “future” ZAPs. I have seen some posts about getting AT data into GS, along with some pre-written scripts to do so. Let me start by saying that I know very little about scripting. Looking for advise/assistance in completing an efficient Integration from AT > GS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |