Thanks for the reply! I’ll add that note about record size to our README. In its simplest form, this is a flawed model if (and only if) you need to perform any logic based on the historical value of any given field. But even this can be overcome by ...

here is a mildly tested airtable poller that someone from our local mutual aid group whipped up! https://github.com/crownheightsaid/airtable-change-detector it could probably be run on heroku for free every 10 minutes using the scheduler