Hi-
Currently for every table automation that we want to sync to an external database SQL we need to configure three separate automations- one for insert records, one for modify records and one for delete records.
It would be ideal if an automation can be triggered by either the record being inserted OR the record being modified. That would help Tulip users by needing less automations that are otherwise the same! Each automation needs monitoring on the history to make sure it is still working, etc and any changes need to be made in multiple places.
Thanks!
Mike
Hi Mike,
Thank you for the feedback - agree that maintaining multiple Automations is cumbersome.
In the future ideally we should allow the Automations Builder to specify more complex logic for when a specific Automation is triggered. This could involve combining rules for Table field updates.
The next projects we’re taking on for the Automations roadmap is to make events themselves more granular - e.g., listening for Column updates, not just row updates as there’s no easy workaround that avoids blank runs without having finer granularity.
Great to know that bundling Table events could be a first step into combo event triggering logic. We’ll take this into account as we plan the next group of Automations improvements in the next couple of months.
Other Community readers – Please weigh in on this thread if you’re also running into this problem (having to create Automations that do the same thing for several different Event Types), with the use case and event types you’d like to combine.
1 Like