Skip to content

Supported connectors

Data Workers ships 50+ connectors across the stack. They fall into two families:

  • Catalog connectors — the systems agents read metadata, lineage, and schemas from.
  • Enterprise connectors — the operational systems around your data: orchestration, alerting, quality, BI, observability, identity, ITSM, cost, and streaming.

Connect a system by setting its environment variables (terminal path, all plans) or through the connector panel (Spellbook console, Scale — a subset of this list has console cards today). Either way, a system only shows 🟢 Connected after a live verification test passes.

Snowflake · BigQuery · Databricks (Unity Catalog) · AWS Glue · AWS Lake Formation · Hive Metastore · dbt · DataHub · OpenMetadata · Microsoft Purview · Google Dataplex · Nessie · Apache Iceberg (incl. REST catalog) · Apache Polaris · OpenLineage/Marquez · PostgreSQL · Redshift

Detailed setup pages, with exact environment variables and minimum grants:

For catalog systems without a dedicated page, ask your agent — “How do I connect Dataplex?” — and it will name the variables it needs; the least-privilege guidance applies to all of them.

CategorySystems
OrchestrationAirflow, Dagster, Prefect, AWS Step Functions, Azure Data Factory, dbt Cloud, Cloud Composer, Temporal, Mage, Kestra, Argo
Ingestion / ELTFivetran, Airbyte, Stitch, AWS DMS, Debezium, dlt
AlertingPagerDuty, Slack, Microsoft Teams, OpsGenie, New Relic
QualityGreat Expectations, Soda, Monte Carlo, Anomalo, Bigeye, Elementary
BILooker, Tableau, Metabase, Sigma, Superset
ObservabilityOpenTelemetry, Datadog
IdentityOkta, Azure AD
ITSMServiceNow, Jira Service Management
CostAWS Cost Explorer
StreamingKafka Schema Registry
MLMLflow, Weights & Biases

Not natively supported (we say so plainly)

Section titled “Not natively supported (we say so plainly)”
  • Atlan, Alation, Collibra — no native connector today. There’s a well-trodden path anyway: read the straight answer.
  • Anything not on this page. If your system is missing, request it — connector priority is demand-driven — or build your own with the @data-workers/catalog-provider-sdk (zero runtime dependencies, ships with a conformance kit).

The Spellbook console accepts Paste schema / CSV: drop in DDL or a CSV of your tables and the agents work with that as a starting catalog — useful for evaluations and for systems that will never get a connector.