This seems like functionality that should have been in the product a long time ago.
Considering that a frequently used zap would entail Unsubscribers in Mailchimp or whatever email automation service… it’s reasonable to expect that in this scenario, the Airtable user would want to simply delete the record, rather than move it or update it or whatever.
That this BASIC functionality was requested 3 years ago and hasn’t been addressed is a little troubling.
Database product designer are [typically] quick to come up with a variety of ways to create information, but when it comes to archive policies, janitorial processes, and helping users embrace normalization standards, they typically shrug their shoulders and point to their APIs.
A well-designed data system - especially one that is designed for code-free living - should be prepared to [natively] implement janitorial actions that not only sustain a clean data climate, but also maintain performance. It’s in Airtable’s best interest to assist users concerning the health of their data assets.
In any case, Integromat is certainly an option as is the Airtable API. One of the challenges in data maintenance is performing deletions where dependencies exist and code-less integration tools are less likely to help you avoid creating orphaned records.
We built a tool that always deletes any record in a certain view. So you can setup a view filter(s) with any criteria that you like and when matching records are detected, they will automatically get deleted.