Skip to main content
Version: 2.0-beta.1

Connector Nodes: Bridge to Your Industrial Ecosystem

MaestroHub's Connector Nodes connect pipelines to shop-floor assets and enterprise systems with reusable, production-ready integrations. Configure a connection once, share it across teams, and keep data moving without custom code.

Key Benefits​

  • Unify access to PLCs, databases, and APIs through the same drag-and-drop node experience
  • Reuse connection profiles so credentials and security settings stay consistent
  • Run with industrial reliability thanks to retries, pooling, health monitoring, and audit trails
  • Scale confidently knowing every connector ships with guardrails for security and governance

What You Can Connect​

  • Industrial protocols: Modbus (TCP/RTU/ASCII), OPC UA, Siemens S7
  • Databases: PostgreSQL, Microsoft SQL Server (more on the roadmap)
  • Modern interfaces: MQTT v3.1/v5, REST/HTTP, with GraphQL and gRPC coming soon
Growing Catalog

We continuously add new connector nodes—check release notes or reach out if you need an integration that is not listed yet.

Core Concepts​

Connection Profiles​

Define how MaestroHub reaches an external system—host, port, credentials, certificates, and performance settings. Update the profile once and every pipeline using it stays in sync.

Functions​

Describe the action to perform on that system—read coils, execute queries, publish messages, and more. Functions validate parameters, handle retries, and expose only the options that make sense for the chosen protocol.

Separation of Concerns

Connection = Where you connect · Function = What you do there. Test them independently, then mix and match inside any pipeline.

Quick Start​

  1. Open the Connect area, choose New Connection, and create a profile for your PLC, database, or service. Test and save it.
  2. Add functions under that profile for the operations your team needs—reads, writes, queries, publishes, subscribes.
  3. Drop the matching connector node into a pipeline, pick the profile and function, then map any required parameters or timeouts.

Design in Pipelines​

  • Drag nodes from the Connectors shelf and place them exactly where data needs to enter or leave your flow.
  • Select the appropriate connection profile and function from filtered dropdowns—only valid combinations appear.
  • Map parameters with literals or expressions (e.g., payload.orderId, context.shift). Optional overrides cover retries, logging, and timeout behavior.
  • Collect sensor data via Modbus and stream it to historians or MQTT topics for live monitoring.
  • Synchronize production orders by pulling from SQL/REST systems and pushing new instructions to Siemens S7 PLCs.
  • Route alarms by subscribing to MQTT topics, enriching with database context, and publishing alerts to downstream systems.