Overview
Connector Management allows users to create and maintain connections to external data sources within Datanyx. Connectors serve as reusable configurations that enable data ingestion from cloud storage, databases, and third-party applications.
Use Connector Management to:
- Establish connections to supported external systems
- Centralize and standardize data source configurations
- Enable data pipelines and reports to access external data
Connectors are accessed from Data Source → Connector Management. The page lists all connectors visible to the signed-in user and provides creation, edit, delete, and search controls.
When to use it
- A new external system needs to be made available to Reports, Workflows, or deidentification jobs.
- An existing credential set has changed and the connector definition needs updating.
- A connector is no longer in use and should be removed to keep the registry clean.
- Multiple Designers need to reference the same data source under a single, governed configuration.
Supported connection types
Datanyx supports ten connection types, grouped by category:
- Cloud object storage: Amazon S3, Azure Blob Storage, AWS
- File transport: FTP, File Location
- Data warehouses and platforms: Amazon Redshift, Databricks
- SaaS applications: Salesforce, Jira, Smartsheet
Configuration reference
Each connection type requires a specific set of fields.
| Connection Type | Required Fields |
|---|---|
| FTP | Host name, Port, Username, Password, File path |
| Amazon S3 | Secret key, Access key, Region, Bucket name |
| Azure Blob Storage | SAS URL, Base URL, Container name |
| File Location | Local file path |
| Databricks | Host name, Access token |
| Smartsheet | Access token |
| Jira | Domain URL, Username, API access token |
| Salesforce | Username, Password, Security token or Consumer key |
| Amazon Redshift | Port, Database name, Schema name, Username, Password |
| AWS | Secret key, Access key, Region |
Connector list columns
| Connector name | User-supplied identifier |
| Connection type | One of the ten supported types |
| Created by | User who originally created the connector |
| Created date | Timestamp of creation |
| Settings | Edit and delete actions |
Key behaviors
Reusability across products. A connector created by any Designer is available to all products the user has rights to. A Weave Designer who creates a Salesforce connector makes it available for Lens Reports and Maskbits jobs as well, subject to those Designers’ product roles.
Credential storage. Secrets (passwords, access keys, tokens) are stored encrypted and are never displayed back in the edit form after save; replacing a secret requires re-entry.
Impact on downstream artifacts. Editing a connector’s credentials is transparent to Reports and Workflows that reference it. Editing the connection type is not supported — change of type requires a new connector.