databricks-lakeflow-connect

Build managed ingestion pipelines from SaaS apps and databases into Databricks Unity Catalog.

4|1|Updated May 22, 2026
One-click install
npx skills add https://github.com/ThomazRossito/ai-data-agents --skill databricks-lakeflow-connect-thomazrossito
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: databricks-lakeflow-connect
Source: https://github.com/ThomazRossito/ai-data-agents/tree/main/plugins/ai-data-agents/skills/databricks-lakeflow-connect
Command: npx skills add https://github.com/ThomazRossito/ai-data-agents --skill databricks-lakeflow-connect-thomazrossito

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Moving data from SaaS applications (Salesforce, Workday, ServiceNow, GA4, HubSpot, Confluence) and databases (SQL Server, PostgreSQL, MySQL) into Databricks normally requires custom connector code, credential management, and CDC handling. This Skill guides you through Lakeflow Connect, the managed ingestion path that lands governed Delta tables in Unity Catalog using serverless pipelines. ## Core Features & Use Cases - Connector selection guidance: Decide between Lakeflow Connect, Auto Loader, Lakehouse Federation, Delta Sharing, and Zerobus based on where your data lives and whether you need a copy. - Pipeline authoring patterns: Create ingestion pipelines via databricks pipelines create --json or Declarative Automation Bundles, with correct ingestion_definition structure and UC CONNECTION setup. - Database CDC architecture: Configure the gateway pattern for SQL Server (cloud and on-prem) with change tracking vs CDC trade-offs, staging volumes, and network requirements. - Troubleshooting and monitoring: Query event logs, resolve duplicate-key violations, watermark issues, and OAuth connection problems. - Use Case: You need to sync Salesforce Account and Opportunity objects into Unity Catalog nightly. This Skill walks you through creating the OAuth U2M connection in Catalog Explorer, authoring the ingestion pipeline as a DAB resource, and scheduling it with a Jobs pipeline_task. ## Quick Start Use the databricks-lakeflow-connect skill to create an ingestion pipeline that pulls Salesforce Account and Opportunity tables into my main.salesforce_raw schema.

Frequently Asked Questions about databricks-lakeflow-connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ingest Salesforce data into Databricks Unity Catalog?▼

Create an OAuth U2M connection in Catalog Explorer, then author an ingestion pipeline with an ingestion_definition block naming the connection and listing source tables. Schedule it with a Jobs pipeline_task since Lakeflow Connect supports triggered runs only.

Lakeflow Connect vs Auto Loader: which should I use for ingestion?▼

Use Lakeflow Connect for SaaS apps and databases with managed connectors, where CDC and schema evolution are handled by the platform. Use Auto Loader for files on cloud object storage like S3, ADLS, or GCS where you need custom parsing control.

Does Lakeflow Connect support continuous streaming pipelines?▼

No, Lakeflow Connect is triggered-only and rejects continuous: true at pipeline creation. Set continuous: false and schedule runs with a Jobs pipeline_task using a cron or interval trigger.

How do I set up SQL Server CDC ingestion into Databricks?▼

Enable change tracking or CDC on source tables, create a UC connection, then deploy two pipelines: a gateway pipeline on classic compute in your network and a serverless ingestion pipeline that applies staged change events to Delta tables.

Why does my Lakeflow Connect pipeline run but land no data?▼

The UC connection may not be in READY state, or the destination schema may be missing. Run DESCRIBE CONNECTION to verify state, confirm the schema exists, and check the pipeline event log for pre-flight errors.

What are the limitations of Lakeflow Connect connectors?▼

Most SaaS connectors cap at 250 tables per pipeline, Salesforce auth is OAuth U2M only, and database staging volumes retain data for 30 days by default. Source data-type changes typically require a full snapshot reload.