Events and properties
Events trigger workflows.

Event properties
Events have different properties depending on the type of event. An event is always the top element in a workflow. When you select the event, the property editor appears in the panel on the left.

The Properties section lists all events associated with the selected element. In the Only when section, you can add conditional expressions that determine whether the event runs.
General event and action properties are described in the article below:
The workflow property editorFrontend 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)
Last updated
Was this helpful?