Integration Layer

Connectors: From Source Access to Trusted Data

Connector setup is designed for business and analytics teams. Use this guide to configure implemented connectors, validate access, and launch ingestion quickly.

Implemented Connector Matrix

Connector	Type	Preview	Metadata	Extract	Notes
Postgres	Database	Yes	Yes	Yes	Optional SSL and SSH tunnel
MySQL	Database	Yes	Yes	Yes	Optional SSL
SQL Server	Database	Yes	Yes	Yes	Supports trusted and SQL auth, optional SSH
MongoDB	NoSQL	Yes	Yes	Yes	Collection-based extraction
Supabase	Database	Yes	Yes	Yes	Uses Postgres-compatible access path
Snowflake	Warehouse	Yes	Yes	Yes	Warehouse/database required
Databricks	Warehouse	Yes	Yes	Yes	Token + HTTP path based
CSV	File	Yes	Yes	Yes	S3 upload URL flow
Excel	File	Yes	Yes	Yes	Supports multi-file and sheet selection
S3	Object Storage	Yes	Yes	Yes	Bucket/object-based listing
Google Drive	Cloud Drive	Yes	Yes	Yes	OAuth token and item listing support
SharePoint	Content Service	Yes	Yes	Connector-dependent	Tenant/client credentials required

Database Connectors

Setup checklist: validate host reachability, use least-privilege credentials, run connection test, then preview sample records before extraction.

Postgres

Required: host, port, database, username, password. Optional: ssl, SSH tunnel fields.

MySQL

Required: host, port, database, username, password. Optional: ssl.

SQL Server

Required baseline: host and database, then SQL auth (username/password) or trusted connection fields. Optional: encrypt, trustServerCertificate, SSH.

MongoDB

Required: host, port, database. Optional: username/password and ssl.

Supabase

Supported in runtime and treated as a database connector with Postgres-style connectivity fields.

Warehouse Connectors

Snowflake

Required: account, username, password, database, warehouse. Optional: schema, role.

Databricks

Required: host, httpPath, token. Optional: catalog, schema.

File and Object Storage Connectors

CSV / Excel

Use upload URL endpoints first, then create connection with returned S3 URLs. Supports preview and metadata before extraction.

S3

Required: bucket, region, accessKeyId, secretAccessKey.

Cloud Services

Google Drive

Required: accessToken and provider. Supports file/folder listing and scoped extraction.

SharePoint

Required: tenantId, clientId, clientSecret, siteId. Optional: driveId and file path.

Planned / Coming Soon

RedshiftBigQueryNotionHubSpotSalesforce

These connectors appear in broader product messaging but are not currently runtime-enabled in this backend connector factory flow.

Start here: If your source is private, continue to Network and Access.