The workflow property editor

The workflow property editor is where you configure the properties of your app's events and actions. To open it, click the Workflow tab and select an event or action. Changes made in the workflow editor apply only to the specific event or action you're editing.

When you select, or create a new event or action, the property editor opens on the right-hand side of the screen and displays the settings specific to that event or action.

Screenshot showing the workflow property editor in Bubble
When an event or action is selected, the property editor is displayed along the right edge of the browser window.

Every event and action comes with a set of general properties, described below:

General properties

Add a breakpoint in debug mode

"Add a breakpoint in debug mode” property in a Bubble workflow event.
Every event and action has a "Add a breakpoint in debug_mode" property.

When debugging your app, you can choose specific events or actions where execution should pause instead of stepping through every workflow step. Enable this option to add a breakpoint at that point in the workflow.

The breakpoint will only apply when the debugger is active. It has no effect when the debugger is not running, and it will not affect users interacting with the live app.

Enable or disable the debugger: You can enable or disable the debugger from the preview URL of your app. Add the parameter ?debug_mode=true to the URL to enable it. If the URL already contains other parameters, use &debug_mode=true instead. Removing this parameter disables the debugger.

Only when (conditions)

Sometimes a workflow or action should only run when certain conditions are met. For example, when a user is logged in, a checkbox is selected, or a user’s email belongs to a specific domain.

To support this, you can add a condition to the event or action. Conditions are dynamic expressions that evaluate to yes or no. If the condition on an action is not met, that action is skipped. The workflow continues with the following actions, but they will not have access to any data that would have been produced by the skipped action.

Notes

Notes can be added to an event or workflow to remember important things.

Adding notes

Adding notes can be done in two ways:

How to add notes to an action or event.
To add a note to an event or action, click on the Add notes button or select that option from the property editor dropdown.
  1. Click the Add notes button at the top of the workflow canvas.

  2. Click the dropdown menu in the top right corner of the property editor and click Add notes.

If you already have a note on the selected event or action, the label of the button and menu option will change to View notes.

The note editor will open up on the right-hand side of the workflow tab.

Event-specific properties

Frontend events

Frontend events are events that are triggered from a page or view, often as the result of a user action.

Category
Description
Link

General events

General events are triggered upon specific conditions not necessarily initiated by the user interacting with an element, such as when the page loads, a user logs in/out or a specific condition is true.

Element events

Element events are events that are triggered by an element, such as when an element is clicked or its value changes.

Custom events

Custom events can be triggered by other workflows and reused in multiple places.

Backend events

Backend events are events that are triggered server-side (in the backend). They can run independently of pages and views.

Event
Description
Link

API workflow

API workflows are workflows that run on the server rather than in the browser. Unlike regular workflows, they aren't tied to a page or a user session, which means they can run in the background, be scheduled for a future time, or be triggered from outside your app entirely.

The Workflow API (Workflow API section)

A thing is modified

Triggers when a change happens in the database, regardless of source.

Recurring event

Recurring events can be triggered or scheduled and will then run at a specified interval.

Bubble-made plugin events (web)

Event category
Description
Link

Bubble-made plugin events

Events related to plugins made by Bubble.

Action-specific properties

Category
Web/mobile
Description
Link

Account

Both

Actions related to user accounts.

Navigation

Web

Actions related to web-specific navigation.

Navigation

Mobile

Actions related to mobile-specific navigation.

Data (things)

Both

Actions related to the database.

Elements

Both

Actions related to elements.

Email and notifications

Both

Actions related to sending emails and push notifications.

Native mobile actions

Mobile

Mobile-specific actions

Custom actions

Both

Actions related to triggering/scheduling custom events and reacting to database changes.

Bubble-made plugin actions

Web

Actions related to plugins made by Bubble.

In-app purchase actions

Mobile

Actions related to mobile in-app purchase actions (iOS and Android)

Last updated

Was this helpful?