Workiva connector FAQ
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed Workiva ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which tables does the connector support?
The connector supports three source tables: activities (audit activity events), users, and roles. For their schemas, see Supported source tables.
Is ingestion incremental?
The activities table is ingested incrementally, using the activityDateTime field as the cursor. When no start datetime is configured, the connector backfills the previous 365 days by default. The users and roles tables are ingested as full snapshots on each run. See Workiva connector limitations.
Which authentication method does the connector support?
The connector supports OAuth2 client credentials (OAuth M2M) only. You provide a client ID, client secret, and organization ID from a Workiva OAuth2 application. Username and password and API key authentication aren't supported.
How do I get Workiva OAuth credentials?
Create an OAuth2 application in your Workiva organization's developer settings and grant it the activity:read and organization:read scopes. See Configure authentication to Workiva.
Can I control how far back the connector backfills activities?
Yes. Set the start_datetime connector option to a UTC ISO-8601 timestamp to control the start of the first-sync window for the activities table. When omitted, the connector backfills the previous 365 days. See Connector options.