Save the date! Join us on October 16 for our Product Ops launch event. Register here.
Apr 14, 2021 04:14 PM
If I have 2 automations with the same trigger, is there a danger of one automation triggering first, which would prevent the second from triggering?
Here’s my situation. When I enter a deposit amount into a client’s record (“deposit” is “not empty”), an automation does two things:
I want to pull out all of my “send email” actions from other automations, so they are easier to turn off while working on the database. So, if I break that automation into 2 separate automations that both trigger on “deposit” is “not empty”, is there a danger of only one triggering?
Apr 14, 2021 05:52 PM
Personally, if you’re going to do this, I would add another column for “scheduling email sent” or similar. That being a checkbox which is set by the second automation. This way you know for sure the second automation ran.
Apr 15, 2021 10:35 AM
Definitely. There’s no guarantee what the trigger order would be.
I think this is a great plan. Have a single automation that handles all emails, and then have all other automations use that one. How to do that? Webhooks.
You can now use a webhook trigger for automations. Here’s the basic process that I’m picturing:
The number of automations that run is going to increase, so you’ll need to see how that fits into your workspace’s automation allotment. However, with all emails centralized, it would make maintenance of the email system a lot easier.