Connectors: MQTT, OPC UA, Node-RED, Azure IoT Hub, CSV

Choose a way in

Ways to get data into InduQT
Method	Direction	Plan	Use it when
HTTP ingest API	You push	Every plan	You control the sender: a script, gateway, PLC bridge, edge PC or cloud function. The most flexible option, and the fallback for anything not listed.
Excel / CSV file import	One-off upload	Every plan	History from a historian export, data logger or spreadsheet. Best for getting started and for investigating a past event.
Google Sheets / Drive	InduQT polls a URL	Every plan	Readings are logged by hand or by a tool into a sheet, or a system drops a CSV at a stable link. Fetched every 1 minute to 24 hours.
MQTT	InduQT subscribes	Plant Monitor, Enterprise	You already have a broker (Mosquitto, HiveMQ, EMQX, AWS IoT, a gateway’s built-in broker) reachable from the internet.
OPC UA	InduQT reads, or you push	Plant Monitor, Enterprise (cloud); every plan (on site)	PLCs and SCADA expose OPC UA. Use the cloud connector for internet-reachable servers; inside the plant, read with Node-RED or Python and push.
Node-RED	You push	Every plan	An edge box already runs Node-RED, or you need to read Modbus, S7, EtherNet/IP or OPC UA on site without writing code.
Azure IoT Hub / Event Hubs	InduQT consumes	Plant Monitor, Enterprise	Devices already send telemetry to Azure. InduQT reads from its own consumer group alongside your other consumers.
Ignition, Kepware, AWS IoT rules, webhooks	You push	Every plan	Anything that can make an HTTPS POST: Ignition gateway scripts or WebDev, Kepware IoT Gateway REST client, an AWS IoT rule with an HTTPS action, Zapier or any webhook. Send the ingest API format. See the HTTP ingest API.

Whatever the route, data lands in the same place: readings for a machine at a site, keyed by signal. A machine can be fed by several routes at once, for example history from a CSV and live values over MQTT.

Pull connectors

MQTT, OPC UA, Azure IoT Hub / Event Hubs and CSV/JSON URLs are configured as connectors on a site, in the app or with the API. InduQT holds the connection and reports its status.

Connector types
type	Source	Plan	Guide
`mqtt`	MQTT broker	Plant Monitor, Enterprise	Set up
`opcua`	OPC UA server	Plant Monitor, Enterprise	Set up
`eventhub`	Azure IoT Hub / Event Hubs	Plant Monitor, Enterprise	Set up
`http_pull`	CSV/JSON URL (Google Sheets, Drive, SharePoint)	Every plan	Set up

POST /v1/connectors

curl -X POST "https://api.induqt.ai/v1/connectors" \
  -H "Authorization: Bearer $INDUQT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "siteId": "6f1c2c0e-4b1a-4c55-9d0e-1f2a3b4c5d6e",
  "type": "mqtt",
  "name": "Boiler house broker",
  "config": {
    "url": "mqtts://broker.example.com:8883",
    "topic": "plant/+/telemetry",
    "username": "induqt"
  },
  "mapping": {
    "machineFrom": "topic",
    "topicLevel": 1,
    "autoCreate": true
  }
}'

Response

{
  "id": "44c0aa11-2b3c-4d5e-8f60-718293a4b5c6",
  "siteId": "6f1c2c0e-4b1a-4c55-9d0e-1f2a3b4c5d6e",
  "type": "mqtt",
  "name": "Boiler house broker",
  "status": "pending",
  "lastError": null,
  "lastMessageAt": null
}

A new connector starts as pending and moves to connected once InduQT has reached the source. If it cannot connect, lastError says why. Check status with:

GET /v1/connectors

curl "https://api.induqt.ai/v1/connectors" \
  -H "Authorization: Bearer $INDUQT_API_KEY"

Live connectors need the Plant Monitor or Enterprise plan. File imports and the ingest API work on every plan.

Setup guides

HTTP ingest API

Push readings from any script, gateway or service with one HTTPS call.

Set up Excel and CSV import

Load history from a spreadsheet or historian export, in the app or through the API.

Set up Google Sheets and Drive

Publish a sheet as CSV and have InduQT poll it, or import it once by link.

Set up MQTT

Subscribe to a broker and map topics or payload fields to machines and signals.

Set up OPC UA

Read an internet-reachable OPC UA server, or push from a plant server with Node-RED or Python.

Set up Node-RED

A ready-to-import flow that posts readings to the ingest API, or publishes them over MQTT.

Set up Azure IoT Hub / Event Hubs

Read device telemetry from the IoT Hub built-in endpoint or an Event Hub.

Set up

Connectors: getting data into InduQT

Choose a way in

Pull connectors

Setup guides