Workday Activity Logging connector
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Workday Activity Logging from the Previews page. See Manage Databricks previews.
The managed Workday Activity Logging connector in Lakeflow Connect ingests user activity log events from Workday into Databricks.
Feature availability
Feature | Availability |
|---|---|
UI-based pipeline authoring |
|
API-based pipeline authoring |
|
Declarative Automation Bundles |
|
Incremental ingestion |
|
Unity Catalog governance |
|
Orchestration using Databricks Workflows |
|
API-based column selection and deselection |
|
API-based row filtering |
|
SCD Type 2 |
|
Automated schema evolution: New and deleted columns |
|
Automated schema evolution: Data type changes |
|
Automated schema evolution: Column renames |
Treated as a new column (new name) and deleted column (old name). |
Authentication methods
Authentication method | Availability |
|---|---|
OAuth refresh token |
|
OAuth U2M |
|
OAuth M2M |
|
Basic authentication (username/password) |
|
What to know before you start
Before starting, review the Databricks user persona, supported interfaces, ingestion frequency, and common patterns.
Start ingesting from Workday
- Configure Workday for ingestion (Admins). Enable activity logging and create an integration system user, security group, OAuth client, and refresh token.
- Create a Unity Catalog connection (Admins). Create a connection in Catalog Explorer so non-admins can create pipelines.
- Create an ingestion pipeline (Admins or non-admins). Use Declarative Automation Bundles or a Databricks notebook to create a pipeline from an existing connection.