# IoT Logic **IoT Logic** is a no-code/low-code data processing tool built into the Navixy platform. It gives telematics operators direct control over how device data is received, processed, and distributed, without involving a developer for every new requirement. It can work with GPS trackers, dash cams, IoT sensors, or third-party telematics servers forwarding device data into Navixy. Incoming data is normalized into a consistent format regardless of its origin, and can then be enriched with calculated attributes and routed to the Navixy platform, external systems, or both. Inside the flow, you can transform and route data based on real-time conditions, trigger automated actions on devices, and deliver results to the Navixy platform, third-party systems, or both. Continuous data streams, targeted event-driven notifications, and parallel outputs to multiple destinations are all supported within a single flow. ![](/files/TOLIczvSea4eLUNDmjLZ) {% hint style="info" %} **Navigation** IoT logic is accessible to account **Owners** in the **Account Settings** section. To find it: 1. Click the profile icon in the top-left corner of the screen to open your account settings 2. In the settings sidebar, select **IoT Logic** {% endhint %} ## IoT Logic components **IoT Logic** relies on its components to process, decode, enrich, and convert incoming data in real time, ensuring compatibility with various platforms and services. By optimizing data flow management, the solution enhances accuracy and customization of your data-related activities and offers more control over the data involved in your processes in general. ### Flow **Flow** is the central functional element of IoT Logic, providing a structured framework for designing, customizing, and managing data processing. It introduces an intuitive drag-and-drop workspace that simplifies the creation of data pipelines through a sequence of data processing steps - **Nodes**. The process is built around three key stages of data interaction: data reception, data enrichment, and data transmitting, each handled by specific nodes. Here are the most common ones: * [Data Source node](/docs/user/guide/account/iot-logic/nodes/data-source-node.md) manages data reception by connecting trackers to the Navixy platform for seamless input. * [Initiate Attribute node](/docs/user/guide/account/iot-logic/nodes/initiate-attribute-node.md) enables data enrichment by renaming and customizing incoming parameters to meet various application requirements. * [IF/THEN Logic node](/docs/user/guide/account/iot-logic/nodes/logic-node.md) enables conditional data routing by creating branching points that direct data flow based on logical expressions and real-time conditions. * [Output Endpoint node](/docs/user/guide/account/iot-logic/nodes/output-endpoint-node.md) handles data transmission by forwarding processed data to third-party servers and applications, ensuring efficient delivery. You can build data flows covering your specific use cases or scenarios from scratch, start from a pre-configured template on the IoT Logic start page, or import an existing flow. {% hint style="info" %} For a full list of available nodes with descriptions and guides, see the [Nodes](/docs/user/guide/account/iot-logic/nodes.md) reference page. {% endhint %} ### Expression language IoT Logic uses a built-in expression language based on JEXL (Java Expression Language) with telematics-specific extensions. It powers the data transformation and conditional routing logic inside flows, without requiring scripting or coding. * **Calculation formulas:** compute new data attributes from existing ones using mathematical operations, unit conversions, and bit-level binary decoding. Used in **Initiate Attribute** nodes. * **Condition formulas:** evaluate logical conditions to validate data or branch a flow based on real-time values. Used in **IF/THEN Logic** nodes. For the full syntax reference and function catalog, see the [Navixy IoT Logic Expression Language](/docs/iot-logic-api/technologies/navixy-iot-logic-expression-language.md) documentation. ### Data Stream Analyzer Data Stream Analyzer is a monitoring tool offering real-time troubleshooting capabilities for your data flow. The Analyzer provides a detailed view of incoming device data, making it the primary instrument to assess data integrity. On top of that, it has the potential to minimize operational risks, enhance decision-making, and improve service quality by allowing you to quickly identify data inconsistencies, optimize device performance, and maintain seamless operations. For more details and usage instructions, see [Data Stream Analyzer](#data-stream-analyzer). ### Navixy Generic Protocol Navixy Generic Protocol (NGP) creates the foundation for IoT Logic data handling. It is a flexible communication mechanism designed to standardize data flows from diverse GPS devices and sensors connected to them, enabling seamless integration into a single system. Regardless of the original data format, NGP unifies device communications by converting all incoming data into a common standard, therefore reducing compatibility issues. The protocol ensures reliable, scalable, and secure data transmission, making it ideal for complex fleet management and asset tracking tasks. For technical details and implementation guidance, see the focused [Navixy Generic Protocol documentation](/docs/iot-logic-api/technologies/navixy-generic-protocol.md). ## API access IoT Logic functionality can also be accessed programmatically through the Navixy API. This allows developers to automate flow creation, management, and monitoring. {% hint style="info" %} For security reasons, API access requires appropriate permissions. Contact your account administrator to ensure you have the necessary access rights. {% endhint %} For complete API documentation, parameters, request/response formats, and code examples, refer to the [IoT Logic API documentation](https://navixy.com/docs/iot-logic-api/). ## Section content * [Quick start guide](/docs/user/guide/account/iot-logic/quick-start-guide.md) * [Templates](/docs/user/guide/account/iot-logic/quick-start-guide/templates.md) * [Flow management](/docs/user/guide/account/iot-logic/flow-management.md) * [Default flow](/docs/user/guide/account/iot-logic/flow-management/default-flow.md) * [Flow configuration example](/docs/user/guide/account/iot-logic/flow-management/flow-configuration-example.md) * [Nodes](/docs/user/guide/account/iot-logic/nodes.md) * [Data Source node](/docs/user/guide/account/iot-logic/nodes/data-source-node.md) * [Initiate Attribute node](/docs/user/guide/account/iot-logic/nodes/initiate-attribute-node.md) * [IF/THEN Logic](/docs/user/guide/account/iot-logic/nodes/logic-node.md) * [Device action](/docs/user/guide/account/iot-logic/nodes/action-node.md) * [Webhook](/docs/user/guide/account/iot-logic/nodes/webhook-node.md) * [Output Endpoint node](/docs/user/guide/account/iot-logic/nodes/output-endpoint-node.md) * [Data Stream Analyzer](/docs/user/guide/account/iot-logic/data-stream-analyzer.md) --- # Agent Instructions: 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: ``` GET https://navixy.com/docs/user/guide/account/iot-logic.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.