# Events and properties
Events trigger workflows[^1].
## 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.
Select an event or action to display the property editor and manage properties.
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:
{% content-ref url="/pages/LLilsGUG695atHtijTjV" %}
[The workflow property editor](/core-resources/bubble-workflows/the-workflow-property-editor.md)
{% endcontent-ref %}
## 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.
| Category | Description | Link |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| 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. | [General events](/core-resources/bubble-workflows/bubble-events/frontend-event-properties/general-event-properties.md) |
| Element events | Element events are events that are triggered by an element, such as when an element is clicked or its value changes. | [Element events](/core-resources/bubble-workflows/bubble-events/frontend-event-properties/element-event-properties.md) |
| Custom events | Custom events can be triggered by other workflows and reused in multiple places. | [Custom events](/core-resources/bubble-workflows/bubble-events/frontend-event-properties/custom-event-properties.md) |
### Backend events
Backend events are events that are triggered server-side (in the backend). They can run independently of pages and views.
| Event | Description | Link |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| 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. |
|
| A thing is modified | Triggers when a change happens in the database, regardless of source. | [A thing is modified](/core-resources/bubble-workflows/bubble-events/backend-event-properties/trigger-event-a-thing-is-modified.md) |
| Recurring event | Recurring events can be triggered or scheduled and will then run at a specified interval. | [Recurring event](/core-resources/bubble-workflows/bubble-events/backend-event-properties/recurring-event-properties.md) |
### Bubble-made plugin events (web)
| Event category | Description | Link |
| ------------------------- | ----------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| Bubble-made plugin events | Events related to plugins made by Bubble. | [Bubble-made plugin events](/core-resources/bubble-workflows/bubble-events/bubble-made-plugin-events.md) |
[^1]: A *workflow* is the combination of an event and one or more actions.
Article: [Workflows](/help-guides/logic/workflows.md)\
Reference: [Workflows](/core-resources/workflows.md)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://manual.bubble.io/core-resources/bubble-workflows/bubble-events.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.