> 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/expert-center/fr/faq-and-troubleshooting/iot-logic.md).

# IoT Logic

Connectez Telegram à IoT Logic pour des notifications automatisées et mettez en œuvre un ordonnancement piloté par événements en utilisant des horodatages Unix dans vos flux IoT Logic.

Cette section couvre des scénarios pratiques de configuration d'IoT Logic pour connecter des services externes et mettre en œuvre un ordonnancement personnalisé.

* [Comment connecter Telegram avec Navixy IoT Logic](/docs/expert-center/fr/faq-and-troubleshooting/iot-logic/how-to-connect-telegram-with-navixy-iot-logic.md): Configurez un bot Telegram, récupérez l'ID du chat et configurez un nœud Webhook Point de sortie pour envoyer des messages de télémétrie automatisés depuis IoT Logic.
* [Comment mettre en œuvre un ordonnancement piloté par les événements à l'aide du temps Unix dans IoT Logic](/docs/expert-center/fr/faq-and-troubleshooting/iot-logic/how-to-implement-event-driven-scheduling-using-unix-time-in-iot-logic.md): Construisez un ordonnanceur basé sur le temps Unix dans IoT Logic en détectant les transitions des secondes de la journée entre des paquets consécutifs pour déclencher des Commandes de sortie aux heures cibles.


---

# 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/expert-center/fr/faq-and-troubleshooting/iot-logic.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.