[Public Beta] Database change triggers

Thank you @anna4 & @josh :fire::fire::fire::fire::fire::fire:

Very Excited! Thanks Bubble!

Is this to say we can implement Excel like functionality? Say I have a simple shopping cart example… if the quantity in cart changes, then trigger this workflow to update the total price to equal the new quantity * price?

… but also it could be way more complicated than that.?. like I could instead trigger an API call that does a really fancy computation for me and returns the result to be saved to the database… all from the backend?

This is AMAZING!

1 Like

I guess it depends on how fast the database accepts and processes the data. If someone changes cart items super quick, will it get confused?

Great news. One thing @josh you might want to look adding some paragraph breaks to the manual text :smile: Just to make it more UI friendly!


Love this feature, @josh! Tons of use cases for it and have been experimenting.

A tip for anyone who may not know about it (or forgot about it), use the App Search tool to go through any endpoint you want to convert to a trigger and find each place in your app where you are scheduling that endpoint.


Agreed, this feature is proving super handy and the fact we can reference both the old and new version of the data entry is really useful. Great job guys on this one.

Probably a good call with the rename btw:



Just wanna ask a question, is this good for making some "acitivity log? system? like, when a data is changed, trigger “create new activity log”


@shu.teopengco The short answer is yes, this would make the perfect companion to achieve such a feature like an activity, notification or change log system.


Just tried to use it but it doesn’t involve legacy plans. :frowning:

1 Like


I was wondering if someone could answer my question on a use case.

I have a user thing with nested things inside

So when it comes to downloading the data into one CSV file, what I do is I keep a mirrored thing and I update that with workflows everytime something is changed. Hope your with me.

I’ve been wondering if this Database change trigger is a good use case for above instead of using workflows every time I change a dropdown? I’ve been trying to work out how to use it but I’m struggling a little bit.

Any advice would be great.


This is an amazing and excellent feature which saves a lot of flows and condition of logic running in parallel sometimes we can get very easily lost, thank you.

A small & useful upgrade would be to output a difference between the new thing and the existing thing. This would be really powerful for audit logging.

Finally a selective ‘do not fire change’ check box since there will be workflows running where you do not want it to trigger a database update.


I was trying the same thing and realized All the accounts I have are on legacy plans, seems loyalty is not something Bubble values. :angry:


That’s so disappointing


Indeed. @josh are there any plans to launch this on ALL plans, including legacy?


It’s a bit dirty to exclude features from legacy plans.

It removes the benefit of the legacy plans, forces the upgrade and in my opinion is like a middle finger to the earliest adopters.

Is Bubble still great value for money… yes! But it reduces my confidence in how they will treat users in the future.


I’d have to dis agree that it’s value for money most other platforms out there charge by user not by app

I also said that it’s value for money! I’ll never argue that point if anything Bubble is too cheap!

But withholding features from your earliest adopter plans creates a lack in confidence not only for existing users but more importantly for new users looking to adopt the platform.

I am a massive Bubble advocate but the biggest push back that I get when I try to encourage users to the platform is not the price, the value or the learning curve… it’s the fear of being trapped on a platform where they have zero control over potential future costs!

Forcing users to increase their app costs (regardless of whether it’s $1 or $1,000) will further heighten that apprehension and as such reduce adoption to the platform.

One of Bubbles best policies is that if it goes out of business it will open source which allows us all to build on the platform with confidence. Not that I can see bubble ever going out of business (I’d buy shares if I could!).

The second thing that would make a massive difference is a similar statement surrounding price and legacy users! Give people an incentive to build earlier rather than later!

For the record I have no issues with the later plans having increased capacity etc but restricting features from legacy plans is quite frankly short sighted because even if it reduces confidence in the platform by 1% then whoever made that decision is not doing this wonderful and amazing platform justice!


Hi all,

Thanks all for the positive feedback on this feature. I wanted to address some of the recent replies about how this feature is only available to legacy plans.

For context and history about the current legacy plan situation, I’ll refer you all to this thread started by Josh after the pricing updates from August last year: Pricing updates and thoughts. To reiterate one of his statements:

“we care a LOT about not throwing you under the bus. We completely understand that people are betting their passions on us, and that you are relying on an implicit promise from us to do the right thing to let you continue to be successful.”

We as a company are constantly working to improve the platform in many different ways. One of the ways is with new features that allow more expressivity and power for app creators. Some of these features are rolled out to all plans, including legacy and the Hobby tier - recent features in this category include option sets and the ability to upload large files. We do this when, for example, we feel that a feature is widely applicable to many different kinds of apps, such that any app user, from those just starting off to mature production apps, can benefit.

With other features we choose to place them in a specific paid tier - database change triggers here are an example, as well as the recent Algolia search integration. We feel that features like these give extra oomph to certain users who are generally farther along in their app development process; for example, a person building a prototype on the Hobby tier probably doesn’t yet need the power of Algolia-backed searches. We think hard about the tier that new features are offered in, to see if it makes sense for the value and messaging offered by each tier.

So why did we make a decision to offer new paid features only on the current plans and not legacy? The legacy tiers were created out of a desire to not leave behind anybody who may have bet their project or business on Bubble. If the difference in prices between the legacy and new version of a tier makes a meaningful difference to the economics of your project, we didn’t want to force you to upgrade or be shut out - you can continue on the legacy plan you had before. And after hearing the feedback from the userbase, Bubble decided to give a 2 year period when apps on legacy plans could switch to other legacy tiers - apps on legacy plans will not be left behind, and hopefully by the end of the 2 year period, you’ll know which plan (legacy or otherwise) is suitable for your app’s needs going forward.

Apps on legacy plans are getting the features and improvements that roll out to everybody. However, we feel that since we’re investing in the platform by building new powerful features for users who are further along in their Bubble journey, it is reasonable for us to share in the value that these features bring. If it is important for your app to stay on a legacy plan - please do so. Our hope is to continuously improve the offerings of the current plans such that it’s an obvious decision to switch to a current plan given how much added value the new features provide.

We certainly value our existing users - continuing to empower them and help them grow is a huge part of our daily motivation. As Bubble continues growing and improving, we hope that all our users will continue growing and thriving as well.