> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/app-builder/build-frontend/widgets/trigger-widgets.md).

# Trigger widgets

Trigger widgets capture direct user actions, such as clicks, to execute backend logic.

## Available trigger widgets

* [**Button**](/app-builder/build-frontend/widgets/trigger-widgets/button.md): Captures clicks to execute function sequences.

{% hint style="info" %}

#### Using icons as triggers

The button is the primary widget in this category, but you can also configure [icons](/app-builder/build-frontend/text-icons-and-images.md#icons) as triggers. Icons follow identical data binding rules.
{% endhint %}

## Data binding

Drag from a function or modifier onto the button. The selected slot determines the behavior:

* **Button to function trigger**: A click executes the connected function. The trigger transmits no data. This is the primary direction for trigger widgets.
* **Function output or modifier to widget**: A function output or modifier writes back into a button property. For example, link an output to the `done` property of a [button](/app-builder/build-frontend/widgets/trigger-widgets/button.md) to display a loading animation until that segment of the flow finishes.

The button features a single `onClick` event, so the selection happens automatically when linking a trigger. See [Widgets](/app-builder/build-frontend/widgets.md#data-binding) for the full mechanics.

{% hint style="info" %}

#### Auto-triggering on input

To execute a function automatically from user interface input instead of a click, wire the input of the function to its own trigger. The incoming data feeds and executes the function without requiring a button widget.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.heisenware.com/app-builder/build-frontend/widgets/trigger-widgets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.