> For the complete documentation index, see [llms.txt](https://docs.akenza.io/akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/akenza.io/get-started/rule-engine/rule-input.md).

# Input

The input section is used to define one or more inputs that will trigger the logic. Inputs are usually devices that have sent a data sample to akenza which in turn, triggers the logic block. 

Devices can be selected regardless of their connectivity. As long as they send a data sample to akenza, they will trigger and provide the sample to the specified data source in the logic block. 

Alternatively, a **tag** can be selected as rule input, which will trigger the rule logic for all devices which have the respective tag assigned. Notably, the data scheme for devices assigned to a tag should be the same in order to extract data for comparison in the rule logic.

A device can only be used once per rule and is disabled for selection if it is already added. The search field allows to search devices by name for quick and easy access.

![Rule Input](/files/hAJgqLOwpYwcuOodaWrC)


---

# 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.akenza.io/akenza.io/get-started/rule-engine/rule-input.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.