Connectors
Connectors are an integral part of your application logic that handle the translation between Heisenware and the outside world. They allow your flows to communicate natively with third-party systems, industrial protocols, and external databases.
Connection scenarios
Where a connector executes depends on whether the target system is accessible over the public internet.
Direct cloud connection
If the system is accessible from the public internet (e.g., a cloud API, a web service, or a public MQTT broker), you can use the connector directly in your application backend. The Heisenware platform manages the connection and execution for you in the cloud.
Local connection (via Edge Agent)
If the target system is on a private, isolated network with no inbound internet access (such as a PLC on a factory shop floor), it cannot be reached directly from the cloud.
In this scenario, you must use an Edge Agent (available as a native binary or Docker container).
Customized Native Agent: You can compile a native agent directly inside the App Builder. You decide exactly which connectors and credentials you want to include in the package.
Deployment: Once you have built your custom binary, you install it on a target system within the local network.
Visibility in library: Once the agent is online, it automatically appears in your library. Inside the visual Agent representation, you will find the specific connector classes you selected during the build process.
Edge execution: Using functions from this agent-specific category ensures that the logic is executed directly at the edge, allowing you to integrate local devices seamlessly.
For a deep dive into the build process and deployment options, please refer to the Edge Agent article.
Available Connectors
The following connectors are available. Most of them in both connection scenarios. Each link leads to a detailed guide on configuring and using that specific integration.
Connects directly to Allen-Bradley PLCs for machine data acquisition and control.
Sends and receives emails via SMTP and IMAP.
Reads from and writes to files on a connected file system.
Interacts with any GraphQL API for flexible data queries.
Connects to Heidenhain DNC systems. Always requires a local connection scenario.
Connects to Heidenhain controllers using the OPC UA protocol.
Makes requests to standard web APIs and HTTP endpoints.
Integrates natively with the Manufacturing Integration Platform (MIP) and the corresponding MES Hydra from MPDV.
Controls Kuando Busylight status indicators.
Sends print commands to ZPL-compatible label printers.
Communicates with industrial devices using the Modbus protocol.
Connects to an MQTT broker to publish and subscribe to topics.
Connects to an OPC UA server for industrial automation data exchange.
Deploys an OPC UA server to expose data from your application.
Accesses stats and info from the host operating system.
Connects to external SQL databases.
Communicates with devices over a serial port.
Integrates natively with SAP Digital Manufacturing.
Connects directly to Siemens S7 PLCs for data acquisition and control.
Connects to an external InfluxDB database.
Interacts with Zebra RFID readers and devices.
Internal Storage
Heisenware includes production-ready internal PostgreSQL and internal InfluxDB databases by default. You only need the connectors above if you are linking to your own external database servers.
Last updated
Was this helpful?