Creating Connectors

To create a connector, open a site and go to the Connectors tab, then click + New Connector.

Form fields

Asset (optional)

Optionally select an asset to attach the connector to immediately. If you leave this as "None", the connector is created at the site level and can be attached to assets later.

When you select an asset, the connector name is auto-populated as "[Asset Name] [Protocol Label]" (e.g., "Pump 001 OPC UA").

Protocol Type (required)

Choose the communication protocol:

The protocol selection determines which configuration fields appear below.

Name (required)

A human-readable name for the connector (up to 255 characters). Must be unique within the site. If an asset is selected, the name is auto-generated but can be edited.

Alias (required)

A URL-friendly identifier, auto-generated from the name. Lowercase letters, numbers, and hyphens only. Must be unique within the site.

A green checkmark confirms the alias is available; a red indicator means it is already taken.

Endpoint (required)

The connection address for the data source. Format depends on the protocol:

• OPC UA: opc.tcp://hostname:port/path — the opc.tcp:// prefix is added automatically; enter just hostname:port/path
• Modbus TCP: hostname:port
• REST API: https://hostname/path
• CAN Bus / Edge Device / Custom: protocol-specific address

Protocol configuration

Additional fields appear based on the selected protocol. See the protocol-specific pages for details:

• OPC UA
• Modbus TCP
• Other Protocols

After creation

The connector appears in the site's connectors list. Next steps:

1. Create an edge deployment — if the site does not already have one, create a deployment and install the edge gateway. OPC UA discovery runs on the gateway, so it must be online before you can populate the connector's data model.
2. Attach to assets — if you did not select an asset during creation, attach the connector to the assets that use this data source
3. Discover the data model — once the edge is online with the discovery utility enabled, open the Data Model tab. The readiness banner walks you through any missing prerequisites and starts a discovery crawl from there.
4. Create bindings — bind variables to specific data points in the discovered model