SendGrid connector

Important

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for SendGrid from the Previews page. See Manage Azure Databricks previews.

The managed SendGrid connector in Lakeflow Connect ingests subusers, IP access-management activity, suppression lists, unsubscribe groups, Marketing Campaigns data (contacts, lists, segments, Single Sends, and engagement statistics), and email templates from SendGrid into Azure Databricks.

Feature availability

Feature	Availability
UI-based pipeline authoring	Supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Not supported
Unity Catalog governance	Supported
Orchestration using Databricks Workflows	Supported
API-based column selection and deselection	Supported
API-based row filtering	Not supported
SCD Type 2	Not supported The SendGrid connector ingests full snapshots of each table.
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.

Authentication methods

Authentication method	Availability
OAuth U2M	Not supported
OAuth M2M	Not supported
Basic authentication (username/password)	Not supported
Basic authentication (API key)	Supported SendGrid parent-account API key.

Ingest from SendGrid in 3 steps

Note

Before starting, review the Azure Databricks user persona, supported interfaces, ingestion frequency, and common patterns.

1. Configure SendGrid for ingestion (Admins): Set up SendGrid to authenticate with Azure Databricks.
2. Create a Unity Catalog connection (Admins): Create a connection in Catalog Explorer to store credentials for Databricks to authenticate with SendGrid.
3. Create an ingestion pipeline (Admins or non-admins): Select any supported interface and create a pipeline from an existing connection.