Events
Events trigger workflows.
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 in the user manual.
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.
Backend events
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: The Workflow Tab: Bubble Introduction Series [4/10] Bubble Academy: Understanding Workflow Execution Rules Getting started with Bubble: Workflows and logic: Getting started with Bubble
Events trigger workflows.
They are classified into these types:
Event types
General events
General events are events that trigger a workflow automatically when a condition is true, such as:
User is logged in Triggers when the user is logged in, or logs in. Core reference | Video
User is logged out Triggers when the user is logged out, or when they log out Core reference | Video
Do when condition is true Triggers when the resulting value from a condition equals yes. Core reference | Video
Page is loaded Triggers when the page is loaded, or whenever the Go to page action is used (even if it goes to the same page). Core reference | Video
Do every X seconds Triggers every X seconds, as specified in the event. Core reference | User manual | Video
An unhandled error occurs Triggers whenever any registered error occurs, regardless of what the error is. Core reference | Video
Element events
Element events are events that are triggered when a user interacts with an element, such as clicking a button.
An element is clicked Triggers whenever an element is clicked by the user. Core reference | User manual | Video
An input's value is changed Triggers whenever an input form element's value is updated, such as when the user types something in a text input. Core reference | User manual | Video
A map's marker is clicked Triggers whenever the user clicks the marker in a Maps element. Core reference | Video
A popup is opened/closed Triggers whenever the user opens or closes a popup. Note that open/close are two separate events. Core reference | Video
Custom events
Custom events are events that can be triggered from other events, allowing you to set up "modules" or "functions" that you can use in more than one workflow.
Custom events Can be triggered by an action in a separate workflow. Core reference | User manual
Recurring event (server-side) Triggers once on the server, and then at a specified interval. Core reference
Trigger a custom event when data changes (client-side action) Is set to trigger by an action, and then triggers a custom event on the first instance of a specified change in the database. Core reference
Trigger event
Database trigger event (server-side) Triggers whenever a specific change happens in the database. Core reference | User manual
Last updated
Was this helpful?