User Guide: Configuring Source as QuickBooks and Target as Bizintel360 Datalake
Overview
This guide provides a step-by-step walkthrough for configuring QuickBooks as the data source and Bizintel360 Datalake as the target. It explains how to establish a secure connection, retrieve payment-related data, and transmit the processed information to the Datalake.
The integration uses the access token API to authenticate with QuickBooks and retrieve data from the Payment business object. Depending on user preferences, alternative business objects and OAuth 2.0 authentication can also be configured.
When to Use
This configuration is suitable for organizations that need to ingest QuickBooks payment data into Bizintel360 Datalake for analytics, reporting, or archival purposes.
- When importing QuickBooks payment data into a centralized data platform
- When using API-based authentication with access tokens
- When structured JSON output is required for storage
- When automated data ingestion is needed
How It Works
The integration follows a structured pipeline to retrieve and transform data from QuickBooks before loading it into the Datalake.
- Generate an access token using the OAuth token API
- Extract the access token from the response
- Call the QuickBooks Payment API using the token
- Convert XML responses to JSON
- Filter and format records
- Load processed data into the Datalake
Each operation prepares the data for the next stage, ensuring reliable and structured ingestion.
How to Configure
Data Source Configuration
Step 1: Select Source Type
On the Data Source page, select the source type as API.
Step 2: Create Product
In the Product Name field, select Create New.
Step 3: Provide Product Details
Enter the Product Name and Business Object according to user requirements.
Note: Selecting “Create New” requires providing all necessary configuration details for the API source.
Step 4: Configure Access Token API
To generate the access token, configure the token API with the required headers and body.
- Method: POST
- API Endpoint URL: https://oauth.platform.intuit.com/oauth2/v1/tokens/bearer
- Headers: {“Content-Type”:”application/x-www-form-urlencoded”}
Body parameters:
client_id={{client_id}}&
client_secret={{client_secret}}&
scopes={{scopes}}&
grant_type=refresh_token&
refresh_token={{refresh_token}}
Select the Body type as Text, then click Test to verify access token generation.
Data Operations
Data Extractor
The Data Extractor operation retrieves specific fields from the API response. In this configuration, it is used to extract the access token while excluding other response keys.
Reference Link: Data Extractor
API Operation
The API operation retrieves Payment business object data using the generated access token.
System Tab
In the System tab:
- Select Create New as Product Name
- Enter Product Name and Business Object
- Configure for Payment data retrieval
Test Tab
In the Test tab, configure the following:
- Method: GET
- API Endpoint URL: Refer to QuickBooks API Documentation
- Params: {“minorversion”:”{{minorversion}}”}
- Headers: {“Authorization”:”Bearer {%access_token%}”}
The minorversion parameter enables access to specific API versions.
Note: sprintf is used in headers to pass the access token.
Reference Link: API
XML to JSON
The XML to JSON operation converts XML responses into JSON format. This conversion enables structured insertion into the Datalake.
The API response is stored in the bizdata_dataset_response dataset.
Reference Link: XML to JSON
Eliminate
The Eliminate operation removes unnecessary keys from the dataset before ingestion into the Datalake.
Reference Link: Eliminate
Single-Line to Multi-Line
This operation converts single-line JSON responses into multiline format, separating records for easier processing.
It improves readability and enables efficient application of subsequent operations.
Reference Link: Single-Line to Multi-Line
Data Target Configuration
Step 7: Configure Datalake Target
Configure the Data Target as Bizintel360 Datalake by following the instructions provided in the Datalake ingestion guide.
Link: Datalake Ingestion
Troubleshooting
- Access Token Not Generated: Verify client credentials and refresh token.
- Authorization Errors: Confirm access token is passed correctly in headers.
- Missing Data: Check business object and extractor configuration.
- Invalid JSON Output: Validate XML to JSON conversion settings.
- Datalake Load Failure: Review target configuration and permissions.
Frequently Asked Questions
What authentication method is used in this configuration?
This configuration uses the OAuth token API to generate an access token, which is used for API authentication.
Can I use a different business object instead of Payment?
Yes. Users may configure alternative business objects based on their data requirements.
Why is XML to JSON conversion required?
The QuickBooks API returns XML responses, which must be converted to JSON for Datalake ingestion.
Is OAuth 2.0 supported?
Yes. OAuth 2.0 can be used to retrieve responses directly from the source if preferred.
Where is the API response stored?
The API response is stored in the bizdata_dataset_response dataset.
Notes
- Ensure all credentials are securely stored.
- Always test API connections before deployment.
- Validate extracted fields before loading into production.
- Review logs regularly for integration issues.
- Update minorversion when API versions change.
This guide enables reliable integration between QuickBooks and Bizintel360 Datalake using API-based authentication and structured data processing.
