> 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/pt-br/faq-and-troubleshooting/iot-logic.md).

# IoT Logic

Conecte o Telegram ao IoT Logic para notificações automatizadas e implemente Agendamento orientado a eventos usando timestamps Unix em seus fluxos do IoT Logic.

Esta seção aborda cenários práticos de configuração do IoT Logic para conectar serviços externos e implementar Agendamento personalizado.

* [Como conectar o Telegram com o IoT Logic da Navixy](/docs/expert-center/pt-br/faq-and-troubleshooting/iot-logic/how-to-connect-telegram-with-navixy-iot-logic.md): Configure um bot do Telegram, recupere o ID do chat e configure um nó Webhook de Ponto de Extremidade de Saída para enviar mensagens automatizadas de telemetria do IoT Logic.
* [Como implementar Agendamento orientado por eventos usando tempo Unix no IoT Logic](/docs/expert-center/pt-br/faq-and-troubleshooting/iot-logic/how-to-implement-event-driven-scheduling-using-unix-time-in-iot-logic.md): Crie um agendador baseado em tempo Unix no IoT Logic detectando transições de segundos do dia entre pacotes consecutivos para acionar comandos de saída nos horários-alvo.


---

# 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/pt-br/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.