Data Connectors
Data Connectors are the gateway every Athena workflow reaches your data through. This is the surface where source systems — ERPs, databases, cloud storage, enterprise applications — get linked into ConverSight, with credentials, network paths, and access boundaries managed centrally. Configure a connector once and every downstream surface (Athena queries, Storyboards, autonomous agents) reads from it.
This is primarily a Data Analyst surface (with a Data Engineer handoff for custom transforms). Pre-built connectors cover the major ERP systems — SAP, Oracle, Microsoft Dynamics, NetSuite, Acumatica, SAGE — plus cloud storage, databases, flat files, and APIs. No custom ETL required for the standard cases; the platform reads directly through the connector you configure.
Each connector captures the details ConverSight needs to identify the source and authenticate to it. That makes connections consistent, reusable across datasets, and centrally manageable — change a credential or upgrade an authentication method in one place, and every downstream workflow picks up the change.
Accessing Data Connectors
The Connectors page lives inside the Data Studio module. The Connectors page displays a complete list of existing connectors and also provides an option to create new ones. It serves as a single interface where users can view, create, and manage all connections in one place. To open it, navigate to the Workbench section and select the Data Studio option.
Each connector is displayed as a card with the following details.
| Field | Description |
|---|---|
| Display Name | Shows the name of the connector. |
| Connector Name | Shows the internal, auto-derived technical identifier for the connector. |
| Type | Shows the connector's provider/category, such as GCS, MySQL, or QuickBooks Online. |
| Action | Provides Edit and Delete options for the connector. |
To locate a specific connector when the list is long, type its name into the Search connectors field. The list narrows as you type to show only the connectors whose names match what you enter.
To focus on connectors of a particular kind, use the All Categories filter. Filtering by category limits the list to connectors that match the selected category, which makes it easier to work with one group of connections at a time.
To refresh the connector list, click the Refresh icon. Refreshing reloads the list so it reflects the latest connectors, including any that were recently added or changed.
Creating Data Connectors
The Add Connector action lets users add a connector for any supported data source and walk through its configuration. The following are the steps to add a connector:
Step 1: To create a new connector, click the + Add Connector button.
Step 2: On the Choose Connector Type gallery, select from the list of available connector types supported by ConverSight.
ConverSight supports multiple connector types including Google Cloud Storage (GCS), Amazon S3, Azure Data Lake, PostgreSQL, MySQL, SQL Server, Snowflake, Acumatica Online, Acumatica Preprod, QuickBooks Online, Xero Online, Katana, DataSync OData Source, and Lance-DB.
Step 3: Each connector type has its own authentication method and configuration requirements depending on the selected source system. Provide inputs for all the required fields across the three sections that make up the connector configuration page: Basic Information, Configuration, and Credentials.
Basic Information
This section identifies the connector itself — its name and how it's referenced elsewhere in the platform. These fields stay the same regardless of which connector type is selected.
| Field | Description |
|---|---|
| Display Name | Specifies the display name of the connector. |
| Connector Name | An auto-derived technical identifier based on the display name. |
| Resource Name (CRN) | An auto-generated resource identifier used to reference the connector elsewhere in the platform. |
Configuration
This section contains the fields specific to the selected connector type — details such as a host address, bucket name, or file path, depending on the source system. These fields are non-sensitive: they describe where the data is, not how to authenticate it, and are visible in plain text both while entering them and when reopening the connector later.
Credentials
This section provides the connector's permission to connect to the source system. Depending on the connector type, this could be a password, an access key, or a service account JSON file. These values are encrypted at the moment they're saved, so the platform can use them to connect without ever needing to display them back in plain text.
For JSON-based credentials like GCS, the field is labeled Service Account JSON, with a text area to paste the key contents directly. An Upload JSON button is also available, which simply reads a selected .json file into the field for you — it's a shortcut for pasting the contents in manually, not a separate storage step.
Step 4: After providing all required values, click on the Save Connector button to create the connector.
Editing Data Connectors
The Edit action lets users update the configuration of an existing connector when their data source details change. To edit a connector, click on the Edit button on the connector's card. The connector configuration page opens with the existing connector details populated, so users can review the current settings and update only the values that need to change.
Credentials section in Edit mode
Unlike Basic Information and Configuration, the Credentials section doesn't show the connector's existing saved value by default when editing.
To view or change it, click Load existing credentials. This retrieves the stored value and fills the field with it, so it can be reviewed or replaced. If no change is needed, the field can simply be left blank — the existing credential is kept as-is when the connector is saved.
For JSON-based credentials like GCS, the Upload JSON button is also available here, working exactly the same way it does when creating a connector — it reads a selected .json file straight into the field, whether that's replacing a loaded value or filling the field in from scratch.
Credentials stay hidden by default in Edit mode specifically so that opening a connector to change an unrelated field — such as a bucket name or host address — never exposes a saved secret on screen as a side effect.
Once all required changes are complete, click on the Save Changes button to update the connector.
Deleting Data Connectors
The Delete action lets users remove a connector that is no longer needed. To delete a connector, click on the Delete button on the connector card you want to remove, this removes the connector and its configuration from the platform, so it no longer appears in the connector list.
