Sadly, Airtable doesn’t let you do this unless you write your own custom JavaScript to handle this. Alternatively, you can turn to an external automation platform like Zapier or Integromat to do this. I prefer Integromat because it is more powerful & more visual & more affordable than Zapier.
You cannot combine a condition and a schedule as triggers in the same automation. An automation also cannot contain branching logic to sometimes send an email and sometimes not.
I typically handle this situation for my clients with an “email table” and two automations. The scheduled automation runs a script to see if there is data to warrant sending the email. If an email should be sent, the script creates a record in the “email table”. A second automation actually sends the email when the new record is created.
You cannot combine a condition and a schedule as triggers in the same automation. An automation also cannot contain branching logic to sometimes send an email and sometimes not.
I typically handle this situation for my clients with an “email table” and two automations. The scheduled automation runs a script to see if there is data to warrant sending the email. If an email should be sent, the script creates a record in the “email table”. A second automation actually sends the email when the new record is created.
Thank you. That makes sense. I’m not well-versed with scripts in Airtable so that may be something I’ll need to learn about before I can make this to work the way I want it to. Thanks once again for the suggestion.
Sadly, Airtable doesn’t let you do this unless you write your own custom JavaScript to handle this. Alternatively, you can turn to an external automation platform like Zapier or Integromat to do this. I prefer Integromat because it is more powerful & more visual & more affordable than Zapier.
Thanks, Scott. I prefer Integromat too for the same reasons. I guess that’s the route I’ll take for this one. Thanks once again for the quick response.
Awful way of doing it, but
Schedule Automation: Set field X “On” at 5pm.
Create a formula Y that says “Go” if (Field X == “On” and Tickets > 0)
Logic Automation: When Record Starts Matching Conditions (Y == “Go”), Send email
Schedule Automation: Set field X “Off” at 6pm.
This basically just uses the Scheduler as a primer for a once a day notification. The second scheduled automation resets your setup so that the records can “Start matching conditions” again the next day. It requires 3 automations per day, rather than 1 if Airtable allowed simpler logic.
A more frugal application would be the following formula field and Automation:
If(And(Value(Datetime_Format(Now(), “H”)) > 17, Value(Datetime_Format(Now(), “H”)) < 18, Tickets>0), “Go”, “No”)
Automation: When Record Starts Matching Conditions (Formula == “Go”), Send Email.
The reason I did not lead with this implementation is because the “Now()” feature is unreliable and unpredictable. You will get an email at some point between 5:00 and 6:00, but only the Airtable gods know exactly when.
Awful way of doing it, but
Schedule Automation: Set field X “On” at 5pm.
Create a formula Y that says “Go” if (Field X == “On” and Tickets > 0)
Logic Automation: When Record Starts Matching Conditions (Y == “Go”), Send email
Schedule Automation: Set field X “Off” at 6pm.
This basically just uses the Scheduler as a primer for a once a day notification. The second scheduled automation resets your setup so that the records can “Start matching conditions” again the next day. It requires 3 automations per day, rather than 1 if Airtable allowed simpler logic.
A more frugal application would be the following formula field and Automation:
If(And(Value(Datetime_Format(Now(), “H”)) > 17, Value(Datetime_Format(Now(), “H”)) < 18, Tickets>0), “Go”, “No”)
Automation: When Record Starts Matching Conditions (Formula == “Go”), Send Email.
The reason I did not lead with this implementation is because the “Now()” feature is unreliable and unpredictable. You will get an email at some point between 5:00 and 6:00, but only the Airtable gods know exactly when.
Thanks Cameron. I agree this is pretty convoluted, but nonetheless, a very clever workaround. Thanks a bunch for this response. Really appreciate it.
Awful way of doing it, but
Schedule Automation: Set field X “On” at 5pm.
Create a formula Y that says “Go” if (Field X == “On” and Tickets > 0)
Logic Automation: When Record Starts Matching Conditions (Y == “Go”), Send email
Schedule Automation: Set field X “Off” at 6pm.
This basically just uses the Scheduler as a primer for a once a day notification. The second scheduled automation resets your setup so that the records can “Start matching conditions” again the next day. It requires 3 automations per day, rather than 1 if Airtable allowed simpler logic.
A more frugal application would be the following formula field and Automation:
If(And(Value(Datetime_Format(Now(), “H”)) > 17, Value(Datetime_Format(Now(), “H”)) < 18, Tickets>0), “Go”, “No”)
Automation: When Record Starts Matching Conditions (Formula == “Go”), Send Email.
The reason I did not lead with this implementation is because the “Now()” feature is unreliable and unpredictable. You will get an email at some point between 5:00 and 6:00, but only the Airtable gods know exactly when.
Can you clarify how you pick the record for which you set field X to “On” at 5pm?
Can you clarify how you pick the record for which you set field X to “On” at 5pm?
I assume Burner is using a universally linked record (all records link to one in another table) to provide a roll-up of the Tickets, in which case he can simply write in the record ID of that record into the Automation. Were someone to apply this feature to multiple records (resulting in multiple emails), I would recommend the second feature, as that obviates the hassle of finding/getting records.
Hi @Burner I hope you’re well! I wanted to follow up on this thread and let you know that as of today, conditional automations are now available in Airtable and more information can be found here. I hope this is helpful for your use case!