Backend Workflows
All workflows that do not run on the page
Last updated
All workflows that do not run on the page
Last updated
Backend workflows are workflows executed on the server side of your application. In principle, the heavy actions that run on the backend should be at least a couple of times faster because they are use server resources and not the client. And because they are run server-side they will use your app's available capacity.
Rule of thumb: you should use backend workflows for data changes that require substantial resource availability like the creation of dozens and dozens of database things, making changes to the lists or the result of the change or creation of the object does not have to be immediately visible to the user.
When you create or update a thing on the client side, Bubble is smart enough to display the change first for the User and then make changes to the database behind the scenes. Because of that sometimes it makes sense to build a workflow specifically for client-side as it will provide better UX (changes will be visible faster for the User). For example: adding an item to a shopping cart, or adding 3 newly created items to the list.
Other advanced use cases are for example exposing your endpoints to communicate with 3rd party solutions via webhooks integration.
Read more about server-side actions in the :
Read about how to secure your backend .