Skip to main content

​
Data Pipeline Integration

Data pipeline routes move messages between your Coreflux broker and the systems that surround it — other MQTT brokers, email inboxes, and event streaming platforms. Configure the connection once in LoT, and the broker keeps the data flowing automatically.
Like a postal forwarding service. Mail (messages) sent to your old address (local broker) automatically gets forwarded to your new address (a remote broker, an inbox, or a Kafka topic). You set up the forwarding rules once, and it just works.

​
Pipeline Route Types

MQTT Bridge

Broker-to-broker communication for edge-to-cloud sync and multi-site connectivity.

Email

Send templated notifications and alerts triggered by MQTT messages.

Kafka

Stream data both ways between MQTT topics and Apache Kafka clusters.

​
Choosing a Route

RouteConnects toBest forDirection
MQTT BridgeAnother MQTT brokerEdge-to-cloud sync, multi-site links, backup brokersOut, in, or both
EmailAn SMTP serverHuman-facing alerts and reportsOut only
KafkaAn Apache Kafka clusterHigh-throughput data pipelines, analytics, event replayOut and in
Need to store messages in a database instead? See Data Storage Routes. Need to call an HTTP API? See REST API Routes.

​
Next Steps

MQTT Bridge

Sync topics between two MQTT brokers.

Kafka

Bridge MQTT and Apache Kafka in both directions.
Last modified on July 3, 2026