QuickBooks connector FAQ
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for QuickBooks from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed QuickBooks ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which QuickBooks products does the connector support?
The connector supports QuickBooks Online. To ingest test data, use a QuickBooks Online sandbox company and set the connection's Environment to Sandbox.
Which tables does the connector support?
The connector supports 37 source tables, including lists such as account, customer, vendor, and item, and transactions such as invoice, bill, payment, and journal_entry. For the full list, see Supported source tables.
How far back can the connector ingest data?
For incremental tables, the first sync starts from the start_datetime option. If you don't set it, exchange_rate starts 30 days back and the other incremental tables start 365 days back. Each later sync ingests records changed after the last run. Full-refresh tables reingest all available records on every run.
Does the connector capture deleted records?
Yes, for most tables. Deleted transactions are removed from destination tables on the next sync, and list records that are made inactive in QuickBooks are deleted from the destination table. Deletes for time_activity and tax_agency are applied only when you run a full refresh. See Deleted records.
Which authentication methods does the connector support?
The connector supports authentication using OAuth user-to-machine (U2M) authorization with an Intuit app only. OAuth M2M and basic authentication aren't supported.