> 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/faq-and-troubleshooting/iot-logic.md). # IoT Logic This section covers practical IoT Logic configuration scenarios for connecting external services and implementing custom scheduling. * [How to connect Telegram with Navixy IoT Logic](/docs/expert-center/faq-and-troubleshooting/iot-logic/how-to-connect-telegram-with-navixy-iot-logic.md): Set up a Telegram bot, retrieve the chat ID, and configure an Output Endpoint Webhook node to send automated telemetry messages from IoT Logic. * [How to implement event-driven scheduling using Unix time in IoT Logic](/docs/expert-center/faq-and-troubleshooting/iot-logic/how-to-implement-event-driven-scheduling-using-unix-time-in-iot-logic.md): Build a Unix-time-based scheduler in IoT Logic by detecting seconds-of-day transitions across consecutive packets to trigger output commands at target times. --- # 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://navixy.com/docs/expert-center/faq-and-troubleshooting/iot-logic.md?ask=&goal= ``` `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.