I’m excited to announce that database change triggers are open for public beta testing. They are available on (non-legacy) Person plans and above. If your app is eligible for them, then on the Backend workflows page, you will see:
Special thanks to @anna4, who built out the core of the feature during an internship with us this winter! And thank you to everyone who helped with alpha testing.
Database triggers allow triggering backend workflows when data in your app is modified according to rules you express in the “Only when…” condition. Use cases include:
- Triggering a workflow when you modify data in the Data panel of the editor
- Triggering a workflow when you modify data via the Data API
- Centralizing logic that should happen whenever a certain type of modification is made, to avoid having to manually add a “Schedule API workflow” action in every single workflow in your app that touches that data
I’m particularly excited about that last use case. Lots of apps we see have complicated logic where 20 or 30 workflows are all triggering the same API workflow, because they all need to share logic. Using change trigger workflows, you can make your app a lot simpler and easier to maintain by deleting all those actions.
This feature is in public beta, which means that while we’ve tested it in real apps, do expect to see bugs that have slipped through our testing. Test carefully before depending on it for a mission critical use case. As always, please report bugs here: https://bubble.io/bug_report
There are a number of details, caveats and limitations, so I recommend reading the full documentation before using it: https://bubble.io/reference#Events.DatabaseTriggerEvent