Overview
The Integrations menu bundles functions for connecting external systems. This includes connectors for receiving and forwarding data, and integration flows for event-based processing and distribution.
Main subpages:
Incoming connectors connect external data sources to niotix — typical sources include LoRaWAN network servers (e.g. ChirpStack, Firefly, Things Stack, Loriot) as well as generic inputs such as MQTT (Incoming) and Webhook (Incoming). Depending on the connector, different function profiles are available: device management (synchronisation of create, read, update and delete with the external system), data source for Virtual Devices and Digital Twins, rules and commands (e.g. downlinks), and pure data ingestion.
Outgoing connectors forward data to downstream systems, e.g. via Webhook (Outgoing), MQTT (Outgoing), Kafka or Websocket.
Integration Flows typically follow a fixed processing chain: trigger, optional filter, optional transformation, and delivery to one or more target systems via connectors. Triggers can include data packets, data state changes, or alarm log entries. Transformations allow adaptation to target structures and MIME types, e.g. JSON.
Depending on the use case, integration flows can operate on raw data before state handling or on enriched state data after state handling. Metadata such as Digital Twin, tags, hierarchy, and custom properties can also be included so target systems can process events without additional mapping steps.
In addition to event-based integration flows, the XAPI allows querying historical measurements from the time series database — for example for reporting, BI systems, or scenarios where recipients need defined time ranges rather than live events.
To view and edit this menu item, the all.manage permission is required.