# Trigger Widgets

Trigger widgets are interactive UI elements designed to capture direct user actions and initiate processes in your backend logic.

## Available trigger widgets

* [**Button**](/app-builder/build-frontend/widgets/trigger-widgets/button.md): The standard, highly configurable button. You use it to capture clicks and start your function sequences.

{% hint style="success" %}
**Icons as trigger widgets**\
While the button is the only official widget in this category, you can also use [icons](/app-builder/build-frontend/text-icons-and-images.md#icon) as triggers. They follow the same data binding rules as the button widget.
{% endhint %}

## Connecting to backend logic (data binding)

Trigger widgets connect to your logic by linking an event (like a click) to a function.

### How to link

You link widgets by dragging the logic to the UI:

1. Drag a trigger from a function and drop it onto the widget.
2. A menu will appear on the function block; pick the specific widget event, usually `onClick`, to complete the link. For buttons, there is only one property, so the selection is automatic.

### Two-way interaction

* **To function trigger**: Clicking the button starts the connected logic flow.
* **From function output / from modifier**: A function sends data back to the button. For example, you can link a function's output to a button's `done` property to show a loading animation inside the button until that part of your flow is executed.

{% hint style="success" %}
**Auto-triggering on input**

 You can trigger a function automatically when a user enters data. To do this, connect the function input with the function trigger. In such a case, no extra event (like a click) by the user.
{% endhint %}


---

# 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://docs.heisenware.com/app-builder/build-frontend/widgets/trigger-widgets.md?ask=<question>
```

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.