Zip 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 Zip 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 26 Zip tables, including requests, approvals, purchase orders, invoices, vendors, agreements, payouts, users, and audit-trail event logs. For the full list and the schema of each table, see Supported source tables.
Does the connector support incremental ingestion?
The connector ingests the event_logs table incrementally, using the event timestamp as the cursor. The connector refreshes all other tables on each pipeline update.
Which Zip plans does the connector require?
To ingest the event_logs table, Zip requires a Premier subscription. To confirm that your subscription includes audit-trail export, contact your Zip CSM. See Zip: Extract Audit Trail Events.
Which Zip permissions do I need?
To create the API key that the connector uses, you must be a Zip administrator or have the Manage company API keys Zip permission group. If you use a Restricted API key, it must grant at least Read-only access to each record type you ingest. See Configure authentication to Zip.
Does the connector ingest comments on all Zip records?
No. The connector ingests comments on procurement requests only.