Integration Providers

integration providers the integration module ( /cc/v2 , internally called "cc" for connector cloud) routes litmus edge data to external systems cloud queues, time series dbs, sql databases, mqtt brokers, file stores 45 providers are documented how an instance is built creating an integration instance is a two step graphql chain getproviderschema(providerid " ") returns the full config schema for that provider (field names, types, required, defaults, enums) createinstance(providerid " ", config { }) submits a config matching the schema, gets back an instanceid then you create one or more subscriptions to route tag data into the instance createsubscription(instanceid, topic, ) data starts flowing see create integration instance workflow # for the full chain reference sections on the api portal the api portal at api litmus io includes two cross referenced sections, one entry per provider provider schemas reference (45 entries) one canonical getproviderschema response per provider use as a lookup for valid config fields create instance provider examples (45 entries) one canonical createinstance mutation per provider, with a working config body together, they let you copy a working example and adapt it the 45 providers grouped by category cloud queues / streaming amqp (ssl / tcp) aws iot core, aws sitewise azure event hubs, azure iot hub google cloud pub/sub ibm watson kafka (ssl / tcp / gen 2) mqtt (generic / v5 / ssl) nats splunk time series and data lakes aveva data hub cognite databricks sql influxdb (v1 7 / v2) osi pi historian snowflake databases mongodb (v4+) mysql postgresql sql server oracle fusion cloud other litmus uns rest api (generic outbound http) browse support matrix out of 146 drivers, 38 support browse the browse section on api litmus io includes the full support matrix in its description common browse capable drivers opc ua client advanced (browse + dynamicbrowse + streambrowse) all allen bradley compactlogix/controllogix variants siemens s7commplus, iq r, iq f modbus tcp (limited discovers configured registers, not new ones) mqtt client, rest client (dynamicbrowse for topic / endpoint discovery) see also create integration instance workflow # integration api reference #