Backend workflows for beginners

Where do they run?

Why use them?

  1. If you need to ‘schedule’ some actions in the future, you’ll need to use backend workflows. For example, charge the user after one month when the trial ends; send a reminder a week before an event.
  2. Another benefit is that the user doesn’t have to wait for these background workflows to finish. The user can navigate to another page, start another backend workflow or do anything else. Bubble will handle these workflows in the background, so you won’t notice them.
  3. You are iterating on a big list. With the standard workflows, you can either change a single thing or a list of things together. With backend workflows, you can work on a list one item at a time. This can be useful if you’re working with a big list as you won’t blow up your Bubble application’s capacity.
  4. Your application will be well-organised as you can create a backend workflow and trigger it from various places. You only need to update the workflow once rather than multiple times.

Enabling backend workflows

Enabling backend workflows in NocodeAssistant
Enabling backend workflows

Creating a backend workflow

Scheduling a backend workflow in NocodeAssistant
Defining backend workflow parameters in NocodeAssistant
Backend workflow parameters
Sending email using backend workflows in NocodeAssistant
Sending email using backend workflows

Triggering a backend workflow

Triggering a backend workflow in NocodeAssistant

Scheduling a backend workflow for a future time

Scheduling a backend workflow for a future date in NocodeAssistant
Scheduling for a future date

Cancelling a scheduled workflow

Cancelling a backend workflow in NocodeAssistant
Manually cancelling a scheduled backend workflow

Inspecting the upcoming workflows

Things to look out for

  1. Make sure that you respect the privacy rules of your Bubble application when creating a backend workflow. Check the “Ignore privacy rules when running the workflow” checkbox if you want the backend workflow to override the privacy rules.
  2. Ensure that you give a 3–5 seconds time gap if you’re scheduling multiple backend workflows.

How are they different from database triggers?

  1. Database triggers start automatically when their trigger condition is satisfied. On the other hand, backend workflows require to be triggered using workflows.
  2. You can schedule a backend for a time in future. Database triggers cannot be scheduled.
  3. You can override the privacy settings of your Bubble application with backend workflows. Database triggers will always respect your Bubble application’s privacy rules.
  4. You can manually cancel a backend workflow, but you cannot do the same with a database trigger.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store