Workflows (PE beta)
This core reference entry is suited for beginner-level builders.
Learn more about experience levels.
To learn about this topic more in-depth, we recommend reading the suggested articles below:
Workflows
Logic
Workflows is a part of the Logic series user manual series.
Article series: Logic
Article: The frontend and backend
Article: Dynamic expressions Dynamic expressions are used both to set up conditions, and are highly useful in different actions that you may want to add to your workflows.
Article: Conditions Conditions are used to determine whether a workflow or action should run or not, by checking whether something is true.
Article series: Navigation Using workflows to let the user navigate between pages and page sections.
API workflows
API workflows are workflows that run entirely on the server, can be scheduled to run at a later time and can be triggered from an external app or system using an API call.
Article series: Integrations
Article series: API This article series covers all aspects of inbound and outbound API calls in Bubble.
Debugging
All apps have the occasional bug, and our debugging tools help you squish them efficiently. The debugger helps you go through workflows step by step to see how they perform and the values they return.
Article series: Debugging your application
Bubble Academy: Element videosThe Workflow Tab: Bubble Introduction Series [4/10] Bubble Academy: Understanding Workflow Execution Rules Getting started with Bubble: Workflows and logic: Getting started with Bubble
This is the short-form technical core reference entry for workflows. If you are unfamiliar with how workflows work we recommend exploring the article series below to learn more:
User manual article series: Workflows
Workflows are how your app responds to events. Each workflow starts with a triggering event, such as a button click, followed by a sequence of actions that run in order.
Workflows are managed in the Workflow tab and are scoped to individual pages. The sections below cover all available events and actions.
The workflow tree
The workflow tree displays all workflows on the current page. Each entry represents a workflow event and the actions that run when that event occurs.
By default, workflows are organized into folders. New workflows are placed in the Uncategorized folder unless you move them into another folder. Each folder can be expanded or collapsed to show or hide the workflows it contains. The number next to a folder indicates how many workflows are inside it.
Selecting a workflow in the tree opens it in the editor. From there, you can view or modify the event, its conditions, and the actions that run when it triggers.
Workflow tree filter/view settings
The workflow tree includes several display and organization options available from the settings menu.
Folders
Folders can be used to organize workflows in the workflow tree. You can create folders to group related workflows together, for example by feature or by section of a page.
Folders are only used for organization within the editor. They do not affect how workflows run, the order in which they execute, or what users see in the app.
The workflow editor settings let you group workflows by event type, such as An element is clicked or Page is loaded. Keep this in mind when organizing workflows into folders, since grouping by event type already provides a quick way to navigate and locate workflows.
By Folder / By Event Type
Controls how workflows are grouped in the tree.
By Folder organizes workflows according to folders you create.
By Event Type groups workflows based on their event category, such as Page is loaded, An element is clicked, or Custom event.
Show Conditions
Displays any conditions attached to events directly in the workflow tree. This can help you quickly identify workflows that only run when certain conditions are met.
List View / Grid View Changes how workflows are displayed in the editor area.
List View displays workflows in a vertical list.
Grid View displays workflows in a grid layout, which can make it easier to scan workflows on pages with many events.
General properties
Event and workflow comes with a set of general properties, i.e. properties that are not event- or action-specific.
Add a breakpoint in debug mode
Stops a workflow at the selected event or action when the workflow runs in preview mode.
Only when
A condition that determines whether the event or action runs, defined as a dynamic expression.
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.
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.
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)
Action-specific properties
Email and notifications
Both
Actions related to sending emails and push notifications.
Custom actions
Both
Actions related to triggering/scheduling custom events and reacting to database changes.
In-app purchase actions
Mobile
Actions related to mobile in-app purchase actions (iOS and Android)
Last updated
Was this helpful?