Xero connector FAQ
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Xero from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed Xero ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which Xero plans does the connector require?
The connector requires a Xero organization on a trial or paid Xero subscription. The projects table also requires the Xero Projects add-on subscription. Your app's developer pricing tier sets how many organizations it can connect to and its daily API call limit. See Prerequisites.
Which tables does the connector support?
The connector supports 23 source tables from the Xero Accounting API and Projects API, including invoices, payments, and projects. For the full list, see Supported source tables.
Can one pipeline ingest more than one Xero organization?
No. Each pipeline ingests the one organization that its tenant_id option names. To ingest several organizations, create one pipeline for each organization. See Find the tenant ID.
How far back can the connector ingest data?
For incremental tables, the first sync ingests records modified in the previous 730 days, unless you set the start_datetime option. Each later sync ingests records modified after the last run. Full-refresh tables reingest all available records on every run.
Does the connector capture deleted records?
Yes, for accounts, bank_transactions, credit_notes, invoices, manual_journals, payments, and purchase_orders. Records deleted in Xero are deleted from these destination tables on the next sync. Voided documents stay in the table with Status set to VOIDED. See Deleted records.
Which authentication methods does the connector support?
The connector supports only OAuth user-to-machine (U2M) authorization with a Xero OAuth 2.0 app that you create. OAuth machine-to-machine (M2M) and basic authentication aren't supported.