Skip to main content

Documentation Index

Fetch the complete documentation index at: https://support.entegrata.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Entegrata connectors are the integrations that move data between your source systems and the Lakehouse. They fall into a few broad types — each with its own setup style, authentication options, and operational characteristics. This page covers connector types and the general requirements that apply to all of them. For the full, card-by-card catalog of every specific system Entegrata integrates with, see the Data Connectors page.

Browse all connectors

Full catalog of specific systems Entegrata can collect from and emit to, with per-connector setup guides

​
Connector Types

​
SQL Connectors

SQL connectors read directly from relational databases. This includes generic engines (Microsoft SQL Server, Oracle, Microsoft Fabric SQL / Warehouse / Lakehouse) as well as purpose-built legal platforms whose data lives in SQL Server (Aderant, 3E, Iridium, Intapp, Foundation, and others). Key features:
  • Direct database access — query tables and views in the source with no middleware
  • Schema discovery — tables, views, columns, and constraints are discovered automatically
  • Incremental extraction — pull only changed rows using a cursor column
  • Sync & Delete Operations — most SQL connectors can detect row-level changes without a cursor and soft-delete records removed from the source (see Sync Operation)

​
API Connectors

API connectors integrate with SaaS platforms through their REST APIs — DealCloud, Zoom, ADP, UKG, Microsoft Entra, Dynamics CRM, and others. They handle the operational complexity of REST automatically: authentication, pagination, rate limiting, and retries. Key features:
  • OAuth, API key, or bearer-token authentication
  • Automatic pagination and rate-limit handling
  • Schema discovery from API responses (or OpenAPI specs where available)
  • Scheduled collection with incremental updates

​
Delimited File Connectors

Delimited file connectors ingest CSV / TXT files from a directory on SFTP, Azure Blob Storage, or a local drive. They read flat-file data plus a separate schema definition file that tells the collector how to interpret each file.

​
Supported File Types

Data files:
  • .csv
  • .txt
Only flat directories are processed — subdirectories are skipped during directory expansion. Schema definition files:
  • .csv
  • .xlsx (detected automatically by file contents)

​
Schema Modes

The schema file format depends on the Headers in Schema parameter set on the connection:
  • true (Full Schema mode): The schema definition file contains the full column definition for every table — column names, data types, and primary key flags. Use this when you need explicit control over data types or when your data files do not include a header row.
  • false (Inferred Schema mode): The schema definition file only maps tables to files. Column names are read from the first row of each data file, and data types are inferred from the first 100 rows. Use this when your data files have headers and you want quick setup.

​
Required Schema File Headers

The schema file must contain these columns in the header row:
ColumnRequiredDescription
TABLE_NAMEYesName of the table. Rows with the same TABLE_NAME are grouped into a single resource.
COLUMN_NAMEYesField name in the data file.
DATA_TYPEYesSQL data type (e.g. varchar(50), int, bigint, date, timestamp, decimal, bool).
PRIMARY_KEYNoWhether the column is part of the primary key. Accepts Y/N, true/false, 1/0, y/n, yes/no. Empty = not PK.
FILE_PATHYesPath to the data file, relative to the connection’s directory. Each table needs at least one non-empty value.
Copy-paste header row:
TABLE_NAME,COLUMN_NAME,DATA_TYPE,PRIMARY_KEY,FILE_PATH
Example:
TABLE_NAME,COLUMN_NAME,DATA_TYPE,PRIMARY_KEY,FILE_PATH
employees,employee_id,varchar(12),Y,employees.csv
employees,first_name,varchar(50),N,
employees,last_name,varchar(50),N,
employees,hire_date,date,N,
departments,department_id,varchar(10),Y,departments.csv
departments,department_name,varchar(100),N,
FILE_PATH only needs a value on one row per table — subsequent rows for the same table can leave it blank to avoid repetition. To load multiple files into the same table (e.g. yearly partitions), add additional rows with the same TABLE_NAME and different FILE_PATH values.

​
General Requirements

​
Network Access

Every connector needs network reachability from Entegrata to the source system. For databases and file servers, that usually means firewall or VPN rules allowing Entegrata’s egress addresses; for public APIs, it’s handled for you. See Instance Administration for your instance’s network settings.

​
Credentials

Entegrata stores credentials encrypted at rest and uses them only to authenticate to the source. Credentials are never exposed back to Entegrata users or printed in logs.
Grant read-only access whenever possible. For collector connections Entegrata never needs write, delete, or schema-modification permissions on source systems.

​
Credential Rotation

For connectors using time-bound credentials (API tokens, client secrets, certificates), set the Secret Expiration field on the connection so Entegrata notifies you before the credential expires.

​
Need a New Connector?

If you need a connector that isn’t in the catalog, contact your Entegrata Customer Experience Manager or submit a support ticket.