A few key takeaways, so that you don’t have to watch the whole 30 mins of it:
- When you clone a doc, all table IDs and column IDs remain the same across cloned docs.
- In Zapier, instead of selecting a specific doc to insert/update a row into, you may select Custom value and provide a Doc ID that comes from the first step, along the data.
- These combined will allow you to dynamically specify the target doc, and the automation will still work because table/column IDs are the same. Zapier will complain because it won’t be able to pull table fields from the dynamically specified doc, but the integration will work nonetheless.
- Zapier cannot react on row updates in a source doc, but on row inserts only. The solution is to create a new supporting table and copy the data there as new rows each time the original data changes. See this Krunal’s tutorial
- There’s a gotcha though. Zapier doesn’t pull rows in the order of their creation, so if there are multiple rows for an entry in that supporting table, it may not apply the freshest one last. So whenever you copy a row to the supporting table, make sure that you clean up previous rows for the same entry.