Verkada connector reference

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

This page has reference information for the managed Verkada connector, including supported source tables and destination table schemas.

Supported source tables

The Verkada connector supports the following source tables, all under the default source schema:

Source table	Primary key	Description	Sync mode	Cursor field
audit_log	lw_id	Audit events for your Verkada Command organization, such as sign-ins, configuration changes, and device actions.	Incremental	processed_timestamp
users	user_id	Access-control members in your Verkada organization, including visitors.	Full refresh only

Source table	Primary key	Description	Sync mode	Cursor field
audit_log	lw_id	Audit events for your Verkada Command organization, such as sign-ins, configuration changes, and device actions.	Incremental	processed_timestamp
users	user_id	Access-control members in your Verkada organization, including visitors.	Full refresh only

Connector options

For usage in a pipeline definition, see Examples.

Option	Type	Scope	Required	Applies to	Description
start_datetime	string	Table	No	audit_log	Earliest audit event to ingest on the first sync, as an ISO 8601 UTC timestamp (for example, 2026-07-09T12:00:00Z). Defaults to 365 days before the first sync, and no earlier than 2025-08-12.

Option	Type	Scope	Required	Applies to	Description
start_datetime	string	Table	No	audit_log	Earliest audit event to ingest on the first sync, as an ISO 8601 UTC timestamp (for example, 2026-07-09T12:00:00Z). Defaults to 365 days before the first sync, and no earlier than 2025-08-12.

Destination table schemas

audit_log

Primary key: lw_id Cursor field: processed_timestamp

Field	Data type
lw_id	STRING
timestamp	TIMESTAMP
processed_timestamp	TIMESTAMP
event_name	STRING
event_description	STRING
user_id	STRING
user_name	STRING
user_email	STRING
ip_address	STRING
organization_id	STRING
devices	ARRAY<STRING>
details	STRING
verkada_support_id	STRING

Field	Data type
lw_id	STRING
timestamp	TIMESTAMP
processed_timestamp	TIMESTAMP
event_name	STRING
event_description	STRING
user_id	STRING
user_name	STRING
user_email	STRING
ip_address	STRING
organization_id	STRING
devices	ARRAY<STRING>
details	STRING
verkada_support_id	STRING

users

Primary key: user_id Sync mode: Full refresh only

Field	Data type
user_id	STRING
employee_id	STRING
email	STRING
full_name	STRING
company_name	STRING
department	STRING
department_id	STRING
employee_title	STRING
external_id	STRING
is_visitor	BOOLEAN
has_profile_photo	BOOLEAN
profile_photo_last_updated	TIMESTAMP

Field	Data type
user_id	STRING
employee_id	STRING
email	STRING
full_name	STRING
company_name	STRING
department	STRING
department_id	STRING
employee_title	STRING
external_id	STRING
is_visitor	BOOLEAN
has_profile_photo	BOOLEAN
profile_photo_last_updated	TIMESTAMP

Required Verkada account permissions

The API key that the connector uses must carry Read-only access to the products that back each table. See Configure Verkada.

Permission	Required for
Core (Read-only)	audit_log
Access Control (Read-only)	users

Permission	Required for
Core (Read-only)	audit_log
Access Control (Read-only)	users