> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/es/guide/events-and-notifications/inputs-and-outputs.md).

# Entradas

Reglas de alerta para supervisar sensores y equipos conectados: cambios en entradas discretas, estado de salida, lecturas de sensores dentro de un rango y valores de los campos de estado.

El **Entradas** Esta sección cubre las reglas de alerta para monitorear sensores y equipos conectados en sus dispositivos GPS.

* [**Activación por entrada**](/docs/user/es/guide/events-and-notifications/inputs-and-outputs/input-triggering.md): Alertas cuando una entrada discreta del dispositivo cambia de estado, como un sensor de puerta o Ignición.
* [**Activación por salida**](/docs/user/es/guide/events-and-notifications/inputs-and-outputs/output-triggering.md): Monitorea cambios de estado de las salidas, como el bloqueo del motor o la activación de la alarma.
* [**Parámetro en rango**](/docs/user/es/guide/events-and-notifications/inputs-and-outputs/parameter-in-range.md): Alertas cuando la lectura de un sensor entra o sale de un rango de valores definido.
* [**Valor del campo de estado**](/docs/user/es/guide/events-and-notifications/inputs-and-outputs/state-field-value.md): Notifica cuando un campo de estado del dispositivo alcanza un valor esperado.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/user/es/guide/events-and-notifications/inputs-and-outputs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.