API integration transparency
Connect Xero, QuickBooks and HubSpot through provider-authorised access
Datplan opens the provider's own browser consent flow, uses the permissions granted for supported reporting functions and stores the pulled provider dataset in the local Windows workflow rather than a Datplan-hosted analytics warehouse.
How does a Datplan API integration work?
The user selects a source, signs in with the provider, approves the requested access and chooses an authorised organisation, company or portal. Datplan then requests the supported records, prepares reporting tables locally and records enough run information to show whether the operation completed.
Connection lifecycle
Authorisation, pull, preparation and disconnection remain separate actions
Keeping the stages visible makes it easier to diagnose expired access, provider limits, incomplete pulls and stale reports.
- Select the source and workspaceChoose the correct client or business context before beginning provider authorisation.
- Authorise with the providerSign in through Xero, Intuit or HubSpot and review the permissions shown by that provider.
- Select the authorised tenantChoose the organisation, company or portal that should be associated with the Datplan workspace.
- Run the supported pullDatplan requests the enabled records and reports, handles its supported pagination and observes provider and plan limits.
- Prepare local reporting dataThe Windows app transforms the response into documented reporting grains, dashboards and available export formats.
- Review the runCheck status, timestamps, endpoint results, volume and relevant reconciliation output before using the data.
- Refresh downstream reportsUpdate Excel, Power BI, Tableau or Qlik separately after the Datplan files have been written successfully.
- Disconnect when access is no longer requiredUse Datplan controls where available or revoke the app through the provider's connected-app settings.
Supported live sources
Each integration exposes data suited to a different reporting question
| Provider | Examples of authorised data used for reporting | Typical Datplan output | Detailed page |
|---|---|---|---|
| Xero | Organisations, accounts, contacts, invoices, payments, transactions, reports and ledger information where supported. | Financial summaries, invoice and payment grains, local dashboards, exports and Audit Analytics. | Xero reporting data |
| QuickBooks Online | Company setup, customers, vendors, sales, purchases, payments, credits and accounting reports where supported. | Financial and operational tables, local dashboards, BI files and the same seven Audit Analytics tests as Xero. | QuickBooks reporting data |
| HubSpot | Companies, contacts, deals, owners, pipelines and supported calls, emails, meetings, tasks or notes. | Separate company, contact, deal and activity grains for pipeline, lifecycle and sales-work reporting. | HubSpot reporting data |
| Companies House | Recently incorporated active UK companies and available public-register details in the configured discovery window. | A local discovery table with sector, location, status and incorporation-date filters. | Companies House discovery |
Actual data varies: provider permissions, account subscription, selected Datplan plan, enabled endpoints, API limits and current source availability all affect what can be returned.
Data handling
Separate the local reporting dataset from the service records needed to operate access
Local Windows workflow
- Pulled Xero, QuickBooks and HubSpot provider datasets
- Prepared reporting tables
- Datplan dashboards and layouts
- CSV, JSON and BI export files
- User-created reports and backups
These files must be protected through the organisation's Windows, encryption, folder-permission, retention and backup controls.
Datplan service records
- User and sign-in identifiers
- Source-access and connection references
- Authorised token handling needed for provider requests
- Plan, billing and usage counters
- Run status, security and support records
These records support access and operation; they are not a hosted copy of the provider reporting dataset.
Power BI and other BI tools
The provider connection refreshes Datplan—not the published BI report
A successful source pull updates Datplan's local data. A later export updates the files used by the BI model. Power BI, Tableau or Qlik must then refresh those files through its own configured process.
For Power BI Service, the organisation needs a Microsoft-supported route to the files, such as a suitable gateway or accessible storage arrangement. Track the provider pull, file export and BI refresh as three related but independent results.
Provider access can still fail
An active Datplan plan cannot override an expired authorisation, removed permission, unavailable endpoint, provider outage, API rate limit or quota consumed by another integration. Diagnose the failing stage before starting repeated full pulls.
Disconnecting
Revoke future access and then manage the local copies
Use the relevant Datplan connection controls where available, or revoke the app in the provider's account settings. The provider determines when the authorisation becomes invalid.
Disconnection does not automatically delete databases, dashboards, exports, reports or backups already stored on the user's PC. Review those copies under the organisation's retention and client-data procedures.
Support
Send context, not credentials
For assistance, provide the app version, source, general connection context, affected run time, status and a sanitised error message or screenshot. Do not email provider passwords, tokens, authorisation codes, raw databases or confidential source records.
Integration questions
Understand access, storage and disconnection before connecting
Does Datplan ask for my Xero, QuickBooks or HubSpot password?
No. The provider's own browser sign-in and consent process handles authorisation. Datplan receives the access granted to the app and does not need the user to type the provider password into the Datplan website.
Where are the pulled provider datasets stored?
Supported provider datasets are stored in the local Windows app workflow and user-selected export folders. Datplan does not operate a hosted analytics warehouse for those Xero, QuickBooks or HubSpot reporting datasets.
Does Datplan use any online service records?
Yes. Limited account, sign-in, source-access, token-handling, billing, usage, run-status, security and support records may be processed online where needed to operate the product.
What happens when I disconnect a provider?
Revoking or disconnecting the connection stops future API access after the provider invalidates the authorisation. It does not automatically remove local databases, dashboards, exports, backups or Power BI files already created on the user's device.
Can provider limits stop a Datplan pull?
Yes. A Datplan plan does not override provider permissions, endpoint availability, rate limits, service outages or quota used by another app or user connected to the same provider account.