Appearance
Integrations: Choosing the Right Interface
Last updated
Scada.Ink can exchange data with other systems in several ways. They overlap, so pick by what the other system speaks and which direction the data flows.
| You want to… | Use | Section |
|---|---|---|
| Let a program read or change anything the UI can | REST API /api with a user login | REST API Reference |
| Provision or audit appliances from CI or a fleet script | Configuration API /api/v1 with an API token | Configuration API |
| Give Grafana, Excel or a web page read-only live values | Public Data API (/api/data/tags.json) | REST API Reference |
| Give a reporting tool read-only history | Historian API (/api/data/history.json) | Historian API |
| Publish tags to an MQTT broker / Ignition / a UNS | MQTT Sparkplug B | Sparkplug B |
| Let a SCADA client, HMI or MES browse tags | Built-in OPC-UA server | OPC-UA Server |
| Read or write SQL Server, MySQL/MariaDB, PostgreSQL, Oracle, ODBC tables or MongoDB collections | Remote databases (included tables, named queries) | Remote Databases |
| Stream tag changes, alarms and batches to Kafka, AWS IoT Core, Azure IoT Hub, Google Pub/Sub or MongoDB | Data connectors | Data Connectors |
| Log a snapshot of tag values as a table row on a timer or trigger | Transaction groups | Transaction Groups |
| Push values to a web service on a timer or on change | Outbound REST | Outbound REST |
| Filter, reshape and batch tag changes, alarms, messages or posted events, and route them to tables, HTTP, MQTT, Kafka, tags or workflows with retries | Event Streams | Event Streams |
| Keep writes safe while the network is down | Store & forward | Store & Forward |
| Read data from a device over MQTT/HTTP | A device driver, not an integration | Open Standards, HTTP / Custom |
From inside the appliance
Two lighter options run as part of your own logic rather than as a standing integration:
- Workflows. The Call URL node makes an HTTP request (method, headers as JSON, body; 10-second timeout; the response is stored in a workflow variable,
responseby default, and the node takes its error path on a non-2xx status). The MQTT Publish node publishes a payload to a topic through an existing MQTT device — the device must use the MQTT driver and have write enabled, otherwise the node fails withWrite not enabled for MQTT device <id>. See Communication Nodes. - Scripts.
http.get/post/put/deletecall any URL (10-second timeout; a JSON reply is parsed, and an error status throws), andnamedQueries.run(...)reaches a remote database through a reviewed query. See Scripting API Reference and Named Queries.
Licensing
The REST API, API tokens, the Configuration API and the Public Data / Historian APIs are part of every edition. The built-in OPC-UA server is also included. Sparkplug B (mqtt_sparkplug), remote databases (remote_databases), store & forward (store_forward), transaction groups (transaction_groups) and outbound REST (rest_api_outbound) are licensed features. Data connectors (data_connectors) are included but start switched off. When one is not in your license, or is switched off, its page is missing from the sidebar and its API answers 403 with Feature "<flag>" is not enabled. Check your license or feature settings.