Databricks Lakeflow Connect provides fully-managed connectors for ingesting data from enterprise SaaS applications. Each connector handles source-specific authentication, incremental reads, schema evolution, and automated retries.
Supported connectors
| Connector |
Description |
| Confluence |
Ingest pages, spaces, and comments from Atlassian Confluence. |
| Microsoft Dynamics 365 |
Ingest CRM and ERP data from Microsoft Dynamics 365 using Azure Synapse Link. |
| Google Ads |
Ingest campaign performance and advertising metrics from Google Ads. |
| Google Analytics |
Ingest website traffic and user behavior data from Google Analytics 4. |
| HubSpot |
Ingest CRM, marketing, and sales activity data from HubSpot. |
| Jira |
Ingest project management and issue tracking data from Atlassian Jira. |
| Meta Ads |
Ingest advertising campaign data from Meta (Facebook and Instagram Ads). |
| NetSuite |
Ingest ERP and financial data from Oracle NetSuite. |
| Salesforce |
Ingest CRM records and customer data from Salesforce using incremental reads. |
| ServiceNow |
Ingest IT service management records and tickets from ServiceNow. |
| SharePoint |
Ingest files and list data from Microsoft SharePoint sites. |
| TikTok Ads |
Ingest advertising performance data from TikTok Ads. |
| Workday HCM |
Ingest HR, payroll, and workforce data from Workday Human Capital Management. |
| Workday Reports |
Ingest custom Workday reports into Delta tables. |
| Zendesk Support |
Ingest support tickets, users, and organization data from Zendesk. |
Connector components
A SaaS connector has the following components:
| Component |
Description |
| Connection |
A Unity Catalog securable object that stores authentication details for the application. |
| Ingestion pipeline |
A pipeline that copies the data from the application into the destination tables. The ingestion pipeline runs on serverless compute. |
| Destination tables |
The tables where the ingestion pipeline writes the data. These are streaming tables, which are Delta tables with extra support for incremental data processing. |
Release statuses
| Connector |
Release status |
| Confluence |
Beta |
| Dynamics 365 |
Public Preview |
| Google Ads |
Beta |
| Google Analytics |
Generally Available |
| HubSpot |
Beta |
| Jira |
Beta |
| Meta Ads |
Beta |
| Salesforce |
Generally Available |
| ServiceNow |
Generally Available |
| SharePoint |
Beta |
| TikTok Ads |
Beta |
| Workday HCM |
Beta |
| Workday Reports |
Generally Available |
| Zendesk Support |
Beta |
Feature availability
The following tables summarize feature availability for each built-in SaaS connector. For additional features and limitations, see the documentation for your specific connector.
Confluence
| Feature |
Availability |
| UI-based pipeline authoring |
 Supported |
| API-based pipeline authoring |
Supported |
| Declarative Automation Bundles |
Supported |
| Incremental ingestion |
Supported |
| Unity Catalog governance |
Supported |
| Orchestration using Databricks Workflows |
Supported |
| SCD type 2 |
Supported |
| API-based column selection and deselection |
Supported |
| API-based row filtering |
 Not supported |
| Automated schema evolution: New and deleted columns |
Supported |
| Automated schema evolution: Data type changes |
Not supported |
| Automated schema evolution: Column renames |
Supported
Treated as a new column (new name) and deleted column (old name). |
| Automated schema evolution: New tables |
Supported
If you ingest the entire schema. See the limitations on the number of tables per pipeline. |
| Maximum number of tables per pipeline |
250 |
Dynamics 365
| Feature |
Availability |
| UI-based pipeline authoring |
Supported |
| API-based pipeline authoring |
Supported |
| Declarative Automation Bundles |
Supported |
| Incremental ingestion |
Supported |
| Unity Catalog governance |
Supported |
| Orchestration using Databricks Workflows |
Supported |
| SCD type 2 |
Supported |
| API-based column selection and deselection |
Supported |
| API-based row filtering |
Supported |
| Automated schema evolution: New and deleted columns |
Supported |
| Automated schema evolution: Data type changes |
Not supported |
| Automated schema evolution: Column renames |
Supported
Treated as a new column (new name) and deleted column (old name). |
| Automated schema evolution: New tables |
N/A |
| Maximum number of tables per pipeline |
250 |
Google Ads
| Feature |
Availability |
| UI-based pipeline authoring |
Not supported |
| API-based pipeline authoring |
Supported |
| Declarative Automation Bundles |
Supported |
| Incremental ingestion |
Partially supported
Report tables support incremental ingestion. Resource tables are fully refreshed on each update. |
| Unity Catalog governance |
Supported |
| Lakeflow Jobs |
Supported |
| SCD type 2 |
Not supported |
| Column selection and deselection |
Supported
You can select specific tables. |
| API-based row filtering |
Not supported |
| Automated schema evolution: New and deleted columns |
Not supported |
| Automated schema evolution: Data type changes |
Not supported |
| Automated schema evolution: Column renames |
Not supported |
| Automated schema evolution: New tables |
Not supported |
| Maximum number of tables per pipeline |
250 |
Google Analytics
| Feature |
Availability |
| UI-based pipeline authoring |
Yes |
| API-based pipeline authoring |
Yes |
| Declarative Automation Bundles |
Yes |
| Incremental ingestion |
Yes |
| Unity Catalog governance |
Yes |
| Orchestration using Databricks Workflows |
Yes |
| SCD type 2 |
Yes |
| API-based column selection and deselection |
Yes |
| API-based row filtering |
Yes |
| Automated schema evolution: New and deleted columns |
Yes |
| Automated schema evolution: Data type changes |
No |
| Automated schema evolution: Column renames |
Yes - Treated as a new column (new name) and deleted column (old name). |
| Automated schema evolution: New tables |
Yes - If you ingest the entire schema. See the limitations on the number of tables per pipeline. |
| Maximum number of tables per pipeline |
250 |
HubSpot
| Feature |
Availability |
| UI-based pipeline authoring |
No |
| API-based pipeline authoring |
Yes |
| Declarative Automation Bundles |
Yes |
| Incremental ingestion |
Partially supported. Some tables support incremental ingestion. Other tables require a full refresh. See HubSpot connector reference. |
| Unity Catalog governance |
Yes |
| Orchestration using Databricks Workflows |
Yes |
| SCD type 2 |
No |
| API-based column selection and deselection |
Yes - You can select specific tables to ingest. |
| API-based row filtering |
No |
| Automated schema evolution: New and deleted columns |
No |
| Automated schema evolution: Data type changes |
No |
| Automated schema evolution: Column renames |
No |
| Automated schema evolution: New tables |
Yes |
| Maximum number of tables per pipeline |
250 |
Jira
| Feature |
Availability |
| UI-based pipeline authoring |
Supported |
| API-based pipeline authoring |
Supported |
| Declarative Automation Bundles |
Supported |
| Incremental ingestion |
Supported |
| Unity Catalog governance |
Supported |
| Orchestration using Databricks Workflows |
Supported |
| SCD type 2 |
Supported |
| API-based column selection and deselection |
Supported |
| API-based row filtering |
Supported |
| Automated schema evolution: New and deleted columns |
Supported |
| Automated schema evolution: Data type changes |
Not supported |
| Automated schema evolution: Column renames |
Supported
Treated as a new column (new name) and deleted column (old name). |
| Automated schema evolution: New tables |
N/A |
| Maximum number of tables per pipeline |
250 |
Meta Ads
| Feature |
Availability |
| UI-based pipeline authoring |
Not supported |
| API-based pipeline authoring |
Supported |
| Declarative Automation Bundles |
Supported |
| Incremental ingestion |
Partially supported
Report tables support incremental ingestion. Resource tables are fully refreshed on each update. |
| Unity Catalog governance |
Supported |
| Lakeflow Jobs |
Supported |
| SCD type 2 |
Not supported |
| Column selection and deselection |
Supported
You can select specific tables. |
| API-based row filtering |
Not supported |
| Automated schema evolution: New and deleted columns |
Not supported |
| Automated schema evolution: Data type changes |
Not supported |
| Automated schema evolution: Column renames |
Not supported |
| Automated schema evolution: New tables |
N/A |
| Maximum number of tables per pipeline |
250 |
NetSuite
| Feature |
Availability |
| UI-based pipeline authoring |
Yes |
| API-based pipeline authoring |
Yes |
| Declarative Automation Bundles |
Yes |
| Incremental ingestion |
Yes |
| Unity Catalog governance |
Yes |
| Orchestration using Databricks Workflows |
Yes |
| SCD type 2 |
Yes |
| API-based column selection and deselection |
Yes |
| API-based row filtering |
No |
| Automated schema evolution: New and deleted columns |
Yes |
| Automated schema evolution: Data type changes |
No |
| Automated schema evolution: Column renames |
Yes - Treated as a new column (new name) and deleted column (old name). |
| Automated schema evolution: New tables |
Yes - If you ingest the entire schema. See the limitations on the number of tables per pipeline. |
| Maximum number of tables per pipeline |
200 |
Salesforce
| Feature |
Availability |
| UI-based pipeline authoring |
Supported |
| API-based pipeline authoring |
Yes |
| Declarative Automation Bundles |
Yes |
| Incremental ingestion |
Yes - By default, formula fields require full snapshots. To enable incremental ingestion for formula fields, see Ingest Salesforce formula fields incrementally. |
| Unity Catalog governance |
Yes |
| Orchestration using Databricks Workflows |
Yes |
| SCD type 2 |
Yes |
| API-based column selection and deselection |
Yes |
| API-based row filtering |
Yes |
| Automated schema evolution: New and deleted columns |
Yes |
| Automated schema evolution: Data type changes |
No |
| Automated schema evolution: Column renames |
Yes - Treated as a new column (new name) and deleted column (old name). |
| Automated schema evolution: New tables |
N/A |
| Maximum number of tables per pipeline |
250 |
ServiceNow
| Feature |
Availability |
| UI-based pipeline authoring |
Yes |
| API-based pipeline authoring |
Yes |
| Declarative Automation Bundles |
Yes |
| Incremental ingestion |
Yes - With exceptions when your table lacks a cursor field. |
| Unity Catalog governance |
Yes |
| Orchestration using Databricks Workflows |
Yes |
| SCD type 2 |
Yes |
| API-based column selection and deselection |
Yes |
| API-based row filtering |
Yes |
| Automated schema evolution: New and deleted columns |
Yes |
| Automated schema evolution: Data type changes |
No |
| Automated schema evolution: Column renames |
Yes - Treated as a new column (new name) and deleted column (old name). |
| Automated schema evolution: New tables |
Yes - If you ingest the entire schema. See the limitations on the number of tables per pipeline. |
| Maximum number of tables per pipeline |
250 |
SharePoint
| Feature |
Availability |
| UI-based pipeline authoring |
Supported |
| API-based pipeline authoring |
Yes |
| Declarative Automation Bundles |
Yes |
| Incremental ingestion |
Yes |
| Unity Catalog governance |
Yes |
| Orchestration using Databricks Workflows |
Yes |
| SCD type 2 |
Yes |
| API-based column selection and deselection |
Yes |
| API-based row filtering |
No |
| Automated schema evolution: New and deleted columns |
Yes |
| Automated schema evolution: Data type changes |
No |
| Automated schema evolution: Column renames |
No - Requires full refresh. |
| Automated schema evolution: New tables |
Yes - If you ingest the entire schema. See the limitations on the number of tables per pipeline. |
| Maximum number of tables per pipeline |
250 |
TikTok Ads
| Feature |
Availability |
| UI-based pipeline authoring |
Not supported |
| API-based pipeline authoring |
Supported |
| Declarative Automation Bundles |
Supported |
| Incremental ingestion |
Supported
With exceptions when your table doesn't support incremental ingestion. See Tables that support incremental updates. |
| Unity Catalog governance |
Supported |
| Orchestration using Databricks Workflows |
Supported |
| SCD type 2 |
Supported |
| API-based column selection and deselection |
Supported |
| API-based row filtering |
Not supported |
| Automated schema evolution: New and deleted columns |
Supported |
| Automated schema evolution: Data type changes |
Not supported |
| Automated schema evolution: Column renames |
Not supported
Requires a full refresh. |
| Automated schema evolution: New tables |
Supported
If you ingest the entire schema. See the limitations on the number of tables per pipeline. |
| Maximum number of tables per pipeline |
250 |
Workday HCM
| Feature |
Availability |
| UI-based pipeline authoring |
Not supported |
| API-based pipeline authoring |
Supported |
| Declarative Automation Bundles |
Supported |
| Incremental ingestion |
Supported (selected tables only) |
| Unity Catalog governance |
Supported |
| Orchestration using Databricks Workflows |
Supported |
| SCD type 2 |
Not supported |
| API-based column selection and deselection |
Not supported |
| API-based row filtering |
Not supported |
| Automated schema evolution: New and deleted columns |
Not supported |
| Automated schema evolution: Data type changes |
Not supported |
| Automated schema evolution: Column renames |
Not supported |
| Automated schema evolution: New tables |
Not supported |
| Maximum number of tables per pipeline |
N/A |
Workday Reports
| Feature |
Availability |
| UI-based pipeline authoring |
Supported |
| API-based pipeline authoring |
Supported |
| Declarative Automation Bundles |
Supported |
| Incremental ingestion |
Supported |
| Unity Catalog governance |
Supported |
| Orchestration using Databricks Workflows |
Supported |
| SCD type 2 |
Supported |
| API-based column selection and deselection |
Supported |
| API-based row filtering |
Supported |
| Automated schema evolution: New and deleted columns |
Supported |
| Automated schema evolution: Data type changes |
Not supported |
| Automated schema evolution: Column renames |
Supported
Treated as a new column (new name) and deleted column (old name). |
| Automated schema evolution: New tables |
N/A |
| Maximum number of tables per pipeline |
250 |
Zendesk Support
| Feature |
Availability |
| UI-based pipeline authoring |
Supported |
| API-based pipeline authoring |
Supported |
| Declarative Automation Bundles |
Supported |
| Incremental ingestion |
Supported |
| Unity Catalog governance |
Supported |
| Orchestration using Databricks Workflows |
Supported |
| SCD type 2 |
Supported |
| API-based column selection and deselection |
Supported |
| API-based row filtering |
Supported |
| Automated schema evolution: New and deleted columns |
Supported |
| Automated schema evolution: Data type changes |
Not supported |
| Automated schema evolution: Column renames |
Supported
Treated as a new column (new name) and deleted column (old name). |
| Automated schema evolution: New tables |
N/A |
| Maximum number of tables per pipeline |
250 |
Authentication methods
The following table lists the supported authentication methods for each built-in SaaS connector. Databricks recommends using OAuth U2M or OAuth M2M when possible. If your connector supports OAuth, basic authentication is considered a legacy method.
Confluence
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
Dynamics 365
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
Google Ads
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
Google Analytics
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Supported (API-only) |
| Basic authentication (service account JSON key) |
Not supported |
HubSpot
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
Jira
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
Meta Ads
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
NetSuite
| Authentication method |
Availability |
| OAuth U2M |
Not supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Supported |
Salesforce
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
ServiceNow
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Supported (API-only) |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
SharePoint
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Supported (Public Preview) |
| OAuth (manual refresh token) |
Supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
SQL Server
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
TikTok Ads
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
Workday HCM
| Authentication method |
Availability |
| OAuth U2M |
Not supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
Workday Reports
| Authentication method |
Availability |
| OAuth U2M |
Not supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Supported |
| Basic authentication (username/password) |
Supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
Zendesk Support
| Authentication method |
Availability |
| OAuth U2M |
Supported |
| OAuth M2M |
Not supported |
| OAuth (manual refresh token) |
Not supported |
| Basic authentication (username/password) |
Not supported |
| Basic authentication (API key) |
Not supported |
| Basic authentication (service account JSON key) |
Not supported |
