> 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/navixy-graphql-api/products/iot-logic/guides.md). # Guides Step-by-step guides for IoT Logic in Navixy GraphQL API: building and changing flows, and handling the errors that a write returns. This section contains step-by-step guides for the basic scenarios of using IoT Logic, a product served by Navixy GraphQL API. ### Guides in this section * [Creating and updating flows](/docs/navixy-graphql-api/products/iot-logic/guides/creating-and-updating-flows.md): Create a flow for a group of devices, read it back, replace its graph, enable it, and delete it. * [Reading flows and device data](/docs/navixy-graphql-api/products/iot-logic/guides/reading-flows-and-device-data.md): Find the attribute names of your devices, check what a flow calculated, list flows, and find the flows that a device is in. * [Calculating values in several steps](/docs/navixy-graphql-api/products/iot-logic/guides/calculating-values-in-several-steps.md): Build a chain of nodes where each step reads the values of the previous one, and read earlier values from the history of a device. --- # 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/navixy-graphql-api/products/iot-logic/guides.md?ask=&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.