Watch this video to learn how to use An Element is Clicked Event
This event is triggered when the user clicks on the element. Most visual elements can trigger this event, including texts, buttons, images, and icons.
Our Academy quick tip on how to trigger workflows from inputs
This event is triggered when the value of an input changes. For text inputs, the event is triggered when the user removes focus from the input.
Watch this video to learn more about the Map Marker is Clicked Event
This event is triggered when the user clicks a map's marker. 'This map's current marker' refers to the marker the user clicked.
Watch our Academy quick tip on how to start workflows based on a popup
This event is triggered when a popup opens through a 'Show element' action.
This event is triggered when a popup closes, either through a 'Hide element' action or when the user presses Esc.
Watch this video to learn more about this event
This event is triggered when the user interacts with an element, like clicking a button, and an error occurs. This 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 actual 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. See 'An unhandled error occurs' below to create error handlers that are not element specific.