Flow management

Build custom IoT Logic flows on a visual canvas: connect nodes to receive device telemetry, process and transform data, and route it to external systems.

IoT Logic provides a flexible canvas environment where you can build custom data flows to process, transform, and route device telemetry. Each flow consists of interconnected nodes that perform specific functions within your data processing pipeline, from receiving raw device data to forwarding enriched information to external systems.

Creating a new flow

You create flows from the IoT Logic start page using the Create Flow button.

1. Open IoT Logic. The start page opens with the Created flows table.

2. Click Create Flow.

3. Enter a name and description for the flow and set its initial enabled state.

4. Click Confirm. The canvas opens and the new flow is ready to edit.

Disabled flows don't send any data! The readings from the devices involved in a disabled flow don't reach any destination, including the Navixy platform. This means that disabling a flow can interrupt your monitoring capabilities and data collection for the affected devices. Only disable flows when you deliberately want to stop data transmission completely.

Configuring flow components

IoT Logic flows are built from interconnected nodes that define how data moves through your system. Data enters through Data Source nodes, can be transformed by processing nodes like Initiate Attribute, and exits through Output Endpoint nodes. Additional specialized nodes, like Action and Webhook provide specific functions for automation and integration.

This modular architecture supports both simple data forwarding and complex multi-stage transformations. Every functional flow requires at least one input node and one output node, with optional processing nodes in between to enrich your data according to specific business requirements.

For complete node reference and configuration instructions, see Nodes.

Your flow should include an Output Endpoint node set to Default endpoint mode to send data to the platform. Maintaining this connection ensures your device data remains available for visualization and management in the Navixy interface.

Building your flow

The Nodes pane on the left groups available node types into four labeled sections: Start with and End with (both required), and Process and Action (both optional). For the full list of nodes in each group, see Nodes.

To assemble your data processing sequence:

1. Drag nodes from the left menu and drop them onto the workspace.

2. Click on each node to open its configuration panel and set up the required parameters.

3. Connect nodes by clicking on a node's output connector and dragging it to the input connector of the destination node.

Your flow must begin with at least one Data Source node and end with one or more Output Endpoint nodes. Between these, you can add transformation nodes to manipulate the data according to your requirements.

Nodes can be connected in various configurations:

• A single Data source node can feed multiple nodes for parallel processing

• Multiple Data source nodes can connect to a single Output endpoint node to consolidate data streams

• Initiate attribute nodes can be chained sequentially for multi-stage calculations

Editing existing flows

After creating a flow, you can modify its configuration as your requirements evolve.

Modifying flow details

You can edit a flow's name, description, and enabled state from the IoT Logic start page.

1. Open IoT Logic. Locate the flow in the Created flows table.

2. Click the ... menu for that flow and select Edit.

3. Update the name, description, or enabled state in the dialog.

4. Click Save to confirm the changes.

Removing elements

When you need to restructure your flow, you can remove nodes or connections:

Deleting a node:

1. Click the node you want to remove to display its quick actions

2. Click Delete in the action bar that appears above the node

When you delete a node, all of its connections will also be removed.

Deleting a connection:

• Click on the connection line you want to remove

• Click Unlink or press the backspace key on your keyboard

Managing multiple flows

All flows are listed in the Created flows table on the IoT Logic start page. The table shows each flow's name, last modified date, number of connected devices, and current status.

Each row provides a status toggle to enable or disable the flow without opening it, a download icon to export the flow as a file, and a ... menu with the options Edit, Download, and Delete.

To open a flow on the canvas, click its name in the table or select Edit from its ... menu.

Mapping Table

Next to the page title on the IoT Logic start page, the Mapping Table button opens the Devices mapping dialog, a searchable, account-wide table listing every device and where its data goes.

For each device, the dialog shows:

• Object label: the device's name

• Model: the device model

• Device ID: the device's unique identifier

• Connected flows: the flow(s) the device is assigned to, as clickable links that open each flow

• Data source: the Data Source node feeding the device

Use the search field above the table to filter it by device.

The same device-to-flow assignments are also available programmatically. See Navixy User MCP for the equivalent MCP tool.

Importing and exporting flows

IoT Logic allows you to export flow configurations for backup purposes or to share them with other accounts. You can also import previously exported configurations to quickly set up new flows.

Here's an example of an exported/ready-to-import flow JSON file:

4KB

iot-logic-full-example-exported-flow.json

Open

Exporting a flow

To export your flow configuration:

1. Locate the flow in the Created flows table.

2. Click the ... menu for that flow and select Download.

3. The flow configuration downloads as a JSON file

You can also export a flow from canvas. To do it, open the "..." menu near the flow name and select Download.

What gets exported

The following table shows what is included and excluded from flow exports:

Component	Exported
Node structure and connections	✅
Attribute calculations and expressions	✅
Node names and descriptions	✅
Flow metadata	✅
Device selections (Data Source nodes)	❌
Software-tab push configuration (Data Source nodes)	❌
Authentication headers (Webhook nodes)	❌
MQTT credentials (Output Endpoint nodes)	❌

Device selections, Software-tab push configuration, and authentication data are excluded from exports. Device selections and Software-tab push configuration are excluded to avoid conflicts when importing into a different account. Software-tab mappings reference the node's device selections, so they're excluded along with them. Authentication data is excluded to protect sensitive information.

After importing a flow, you need to manually add the excluded data before you can save the flow.

Importing a flow

To import a flow configuration:

1. On the IoT Logic start page, click Upload Flow

2. Select the JSON file containing the exported flow configuration

3. Review the imported flow structure

4. Configure the excluded elements:

   • Assign devices to Data Source nodes

   • Reconfigure Software-tab push enrichment on Data Source nodes that used it, since it depends on device selections that aren't exported

   • Add authentication headers to Webhook nodes (if applicable)

   • Enter MQTT credentials for Output Endpoint nodes (if applicable)

5. Save the flow

The import process creates a new flow with the structure and calculations from the exported configuration, allowing you to quickly replicate complex data processing pipelines across different environments.

Saving and activating flows

After configuring your flow:

1. Click the Save flow button to store your flow configuration

2. Ensure the flow is enabled for it to begin processing data

Once activated, your flow:

• Receives real-time data from the configured devices

• Applies any defined transformations through Initiate attribute nodes

• Forwards the processed data to your specified endpoints in the Navixy Generic Protocol format

If you need to temporarily disable data processing, you can toggle the flow's enabled status without losing your configuration.

Example configurations

You can find detailed step-by-step descriptions of an example flow creation in Flow configuration example. The example also contains explanations on some common data enrichment options. Feel free to use this example as a template for your custom flows.

For reference documentation on individual node types, including capabilities and configuration options, see the Nodes reference page.