No, I’m very glad you did.
For one thing, your description of how you used Zapier to filter and identify records needing additional work opened my eyes to methods of using middleware beyond simple automation of Airtable actions — which is as far as my work with Zaps had ever taken me.
For another, I came up with three or four ways of almost doing what you wanted to do entirely within Airtable. Some I rejected because they would require you to add manual steps to your process, others because they needed Airtable to do something it currently does not do or to do it differently than it currently does; the former solutions may prove perfectly workable for other bases, and future enhancements of the product could validate the latter. While I failed to find an Airtable-only solution, I better understand the system’s potential and shortcomings.
I’m also glad to find my first reply wasn’t as off the mark as it first appeared. In the context of your application, though, I’m not sure of its benefit, as your approach still seems to require a four-step Zap. Or do you intend to modify your process to take advantage of a formula-crafted record URL?
