Hi @Glenn_Felty, using the approach outlined by @Bill.French is definitely an option and I’ve used an external script and the Airtable API numerous times to achieve something that you can’t do within Airtable on its own, so would wholeheartedly support this approach.
That said, I think it could be done with Airtable and Zapier, although this might depend upon how your base is structured and what your process is. Here’s a simple example, which I appreciate might not work in your context:
Let’s say you’ve got a record in AT for each project and each record has a status field with values such as:
- New Project
- Permit Submitted
- Permit Approved
- Work Started
- Work Completed
You would create a view on your table for each of these statuses, i.e. each view is filtered where Status = “XXXXXXX”
You set up a Zap for each view and when a record achieves the status that puts it into one of the views, the Zap runs and triggers the appropriate action with the appropriate message, e.g. when the project is created (status = New Project) an email is sent to the appropriate people. Sending to multiple people is an option in Zapier (for an email send I think it allows 5 recipients by name or use an email group if you have more). Recipients could be hard coded in the Zap or could be a field value in your AT record for a more dynamic approach.
One constraint in Zapier is that a given record can only be triggered once for each view so if your process means that a record can go from A to B and back again to A, then the 2nd status A won’t be notified by Zapier as it will have already seen the record for status A.
Hope this helps.
JB
