Docs menu
Two ways data gets in: you pull it, or it's pushed to you.
Every integration with an existing system runs through one of two node types — an API node that polls, or a Connection node that receives. Anything beyond these is a custom node (see Extensibility).
Pull on a schedule, or receive as it happens.
API nodes (pull)
Poll an external system on a configurable interval — point it at an endpoint, map the response, and it stays in sync automatically.
Connection nodes (push)
Receive data sent to your workspace directly — the source system pushes, your workspace ingests as it arrives.
What's live today, and what's ahead.
Every claim here reflects what's actually shipped and in use — not a wish list.
| Protocol | Direction | Status |
|---|---|---|
| HTTP Connection | Push | Available |
| Azure IoT Hub Connection | Push | Available |
| API Source (poll) | Pull | Available |
| MQTT | Push | Available |
| AMQP | Push | Available |
| WebSocket | Push | Available |
| OPC UA | Push | Roadmap |
| SCADA | Push | Roadmap |
This table is the authority on what ships.
The Protocol Landscape page compares the building protocols you'll meet in a portfolio — BACnet, Modbus, KNX, DALI, Thread, and SRP. It's industry reference material and makes no claim about connector support. Where a protocol isn't listed above, it isn't a connection node type today; reaching it means a gateway or an edge normalization layer.
The general shape, regardless of protocol.
- Define a connection and choose its protocol
- Point it at an endpoint, broker, or hub
- Map incoming data to your schema
- Publish — data starts flowing into your data tiers (see Cold, Warm & Hot Data)