☁️About backend actions

Not like front-end actions, back-end actions run on Bubble's servers and allow for return values, which mean we can use "Result of step X" values as inputs in other actions. They also bring more security to your actions, since they hide Firebase Credential on the server (hence why many admin and sensible-data-dealing actions are server-sides).

But, as on the front-end, there is a caveat. They are extremely slow to start and run the first time. Though we're not sure how Bubble handles them on the back-end, our guess is that the first time they run, they have to "load the action to the server's memory". This process takes around 20-30 seconds.

After this first execution, they run faster for the next feel minutes, while they are "on the server's memory".

Important! Backend actions to interact with Firebase consume a lot of Workload Units, so we advise to use them only when they are no other alternatives. (e.g. in backend workflows or some actions that are only available to run server-side).

We suggest to always use front-end actions whem possible, for a better user experience, and use backend ones on Bubble's backend workflows, using scheduled actions to trigger them, so that the user won't suffer with long waits. Unless you need the actions return value, in that case, remember to show a loader element to give visual feedback to the user, other them Bubble's loading bar on top.

Back-end actions are also useful when you want to use Bubble and the backend for webhooks from other services.

As backend operations for Firebase run on a firebase-admin instance, they can bypass your Firestore Security Rules, so use them with caution.