> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/dashboard/controls-toolbox/support/trigger.md).

# Trigger

**Category:** Control

**Version:** 1.0

**Last Updated:** April 7, 2026

**Author:** Any2Info

***

### Description

The Trigger control is a helper control that executes dashboard actions at timed intervals while the dashboard is actively displayed.

It enables automated behavior such as refreshing data or navigating between dashboards without requiring user interaction. This makes it particularly useful for scenarios like automatic dashboard rotation or periodic data updates.

The Trigger control is non-visual and does not appear on the dashboard.

***

### Configuration Options

| Setting           | Required | Description                                                                                                                     |
| ----------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Elapsed time      | Yes      | Defines the interval in seconds between each trigger execution.                                                                 |
| Max trigger count | No       | Limits the number of times the trigger executes. If not set, the trigger will continue running until the dashboard is disposed. |

***

### Behavior

* The first trigger execution occurs **after the first elapsed interval**.
* The trigger continues executing based on the defined interval.
* If **Max trigger count** is set, execution stops after the defined number of triggers.
* If **Max trigger count** is not set, execution continues indefinitely while the dashboard remains active.

***

### Actions

The Trigger control can execute any available dashboard action, including but not limited to:

* Refreshing dashboard data
* Navigating to another dashboard
* Triggering automated dashboard rotation

***

### Mappings

The Trigger control does **not support mappings**, as it functions purely as a timed execution mechanism.

***

### Linking

Although the control technically allows linking to other controls, this has **no functional purpose** and should not be used.

***

### Usage

Use the Trigger control when you need to automate dashboard behavior based on time intervals.

Typical use cases include:

* Automatically refreshing data at fixed intervals
* Creating rotating dashboards for display screens
* Running periodic background actions without user input

***

### Tips & Best Practices

* Use a reasonable **elapsed time** to avoid excessive execution frequency.
* Combine with navigation actions to create automated dashboard rotations.
* Avoid unnecessary use of **Max trigger count** unless a finite number of executions is required.

***

### Changelog

| Version | Date          | Change                               |
| ------- | ------------- | ------------------------------------ |
| 1.0     | April 7, 2026 | Initial documentation version added. |


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/dashboard/controls-toolbox/support/trigger.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.