Hi,
I think the root cause of your problem is each table needs it’s own automation, even group of automations. And if I understand well, these automations are similar for each table, each group of automations per table represents some operations, like take value X from Master table and put it to the Table A, field B, all records (or not all, just filtered by some view).
My opinion - scripts and automations are tools to avoid struggle with routine repetitive actions. If you need to create so many similar automations, you just shift the repetitive part to another level. I’m sorry if I mistaken and have incorrect vision of a tool you constructing, but I just want to share my solution when I faced something alike (the need to create a number of automations, X*number of tables).
I just created a single automation with a little scripting.
Fill field F in table T, scope of records defined by view V, value to fill is X
(a little demo below)
For example, look at the line 2
it supposed to fill this table
Here is automation
The last Update step just unchecks Run and write a kind of log (not mandatory). Populating changes done by script.
Which is quite simple.
So, after I check Run, it works as planned.
You can keep as much patterns as you wish, in each new record, sometimes duplicate and edit them, when the target is the same, but other value has to be written, and just check Run against the row you need.
