General Events

User is logged in

This event is triggered when the current user logs in. This can happen on page load, if the user was already logged in, or when the user successfully completes a 'Sign the user up' action.

User is logged out

This event is triggered when the current user logs out. This can happen on page load, if the user was logged out, or when the user successfully completes a 'Log the user out' action. Often a change page action occurs after this event.

Page is loaded

Our Academy quick tip on how to create an event on page load

This event is triggered when the page is loaded. Use this to check the type of user for instance. By adding a condition to an event, the user can be redirected to another page under certain circumstances. A typical case would be 'When the page is loaded' and 'Current user isn't logged in,' go to page 'index.'

Do every X seconds

This event performs an action every X seconds. Bubble updates in real time, so this event will not be used often.


Enter a number in seconds to define the interval.

Do when condition is true

This event is triggered as soon as its condition is true. If 'Run this' is set to 'Just once,' it will run once per page load, either immediately if the condition is true when the page loads or later when it becomes true. If 'Run this' is set to 'Every time,' the workflow is triggered every time the condition is true.

Run this

Choose from 'Just once' and 'Every time' to specify whether the event will run once per page load or every time the condition becomes true.

An unhandled error occurs

This event is triggered if the user interacts with an element, like clicking a button, and there is an error handling for that interaction. This event is only triggered if no 'An element has an error running a workflow' event specific to the element runs. This will execute if the error happens anywhere on the page and happens for both expected errors, such as a failed login attempt, and unexpected errors, such as a bug with the Bubble platform. If no error workflows are defined, the default is to display an alert with an error message. If at least one error workflow runs successfully, i.e., the condition passes and the workflow runs without an error, the error message will not be displayed, and the workflow notifies the user that an error occurred, if appropriate. Use 'Current workflow error' to see the original error message. It has two properties, 'code' and 'message.' 'code' is a short phrase to use in conditions. 'message' is the error message that would display if there were no error workflows. Use 'message' to show the message in an Alert element, for example. Do not use 'message' in conditions since it is language-dependent and can change. 'code' will always be the same no matter what language the app displays. The codes and error messages are listed in the Languages section in the Settings Tab. For error workflows meant to provide a nicer response to unexpected errors, we do not recommend reading data from the database or an external API because if the error is caused by a network or connectivity issue, the error workflow may also fail if it relies on data that cannot be loaded. If the error workflow fails, the user will see an error alert.

Error sources to catch

Choose from 'Any workflow error' and 'Element workflow errors only' to specify whether the event will be triggered by any workflow error (including Do When, When page is loaded, Scheduled events) or just on errors triggered by an element interaction workflow (When element is clicked, when input is changed).