Automation Across Tables in one sourcebase

As of now, automation triggers are limited to one table. Is it possible we could have multiple table sources, doing the same automation, and the outputs are in one or multiple tables as well?

For example: generating an assistant ID

We have different sources of assistants per table. And we have a table that is a masterlist of all the assistant IDs. Instead of having to automate separately for different tables doing the same thing, is there a way that multiple tables can be chosen (or specific views per table) and theyd all flow into the masterlist table that we have?

Thanks!

1 Like

Not directly, no. You could have one Automation per table, where each Automation has a Run a script action that activates an Airtable Automation for the real or main Automation that does what you want.

Also, any time I see someone say “we have multiple tables in a base all feeding into one table in the same base” I am compelled to ask “why are all these different tables, not views”? You may have a much simpler time using views than tables.

2 Likes

Thanks for this! For now, we have multiple data sources (that come from external forms too) that’s why they’re in multiple tables. I’ll try to see if there can be two airtable forms in one table bec that would save me a lot of time for the automation limitation.

You can have a bunch of Airtable forms per table, and I’d bet your external forms can feed into the same table as well as long as they’re not set up to do any data collisions. If all forms are just inserting new records then you should be fine.

1 Like

We’re writing some logic to update systems on our side when data changes in airtable, and our current plan is to use automations to accomplish this. I’m worried that our systems will grow in (appropriate) complexity and end up having more than 25 tables, so without the ability to trigger a shared automation across more tables (or increasing the limit), we will have to investigate adding a Last Modified column and doing a polling system (not our current preference).

also, it’s going to be a PITA to have to maintain the webhook script across 25 automations, when it’s basically the same code (call webhook with table and record id)

(so, +1 for this ask)