Intuit QuickBooks Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to an Intuit QuickBooks location.

Intuit QuickBooks

Create an Intuit QuickBooks Destination

1. Click the + icon on the Nexset that will be sent to the Intuit QuickBooks destination, and select the Send to Destination option from the menu.

2. Select the Intuit QuickBooks connector from the list of available destination connectors. Then, select the credential that will be used to connect to the QuickBooks organization, and click Next; or, create a new Intuit QuickBooks credential for use in this flow.

3. In Nexla, Intuit QuickBooks destinations can be created using pre-built endpoint templates, which expedite destination setup for common QuickBooks endpoints. Each template is designed specifically for the corresponding QuickBooks endpoint, making destination configuration easy and efficient.
   • To configure this destination using a template, follow the instructions in Configure Using a Template.

   Intuit QuickBooks destinations can also be configured manually, allowing you to send data to QuickBooks endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
   • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common QuickBooks endpoints. Each template is designed specifically for the corresponding QuickBooks endpoint, making destination setup easy and efficient.

• To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

  Create Records of a Resource

  Use this endpoint to create records of a specific resource using records from a Nexset. Please see the QuickBooks API document for required record structure.

  • Enter the QuickBooks Online Company ID (Realm ID) in the QuickBooks Online Company ID/ Realm ID field. This is the unique identifier of your QuickBooks company. You can get it from your Settings >> Account and settings >> Billing & Subscription page, or by clicking Control + Option + ? in your account.
  • Enter the type of resource whose records you wish to create in the Resource Type field. This should match the resource type you want to create (e.g., Customer, Account, Invoice, etc.).
  • The endpoint uses POST requests to https://quickbooks.api.intuit.com/v3/company/{realm_id}/{resource_type} where {realm_id} is the QuickBooks Online Company ID you provide and {resource_type} is the Resource Type you provide. The endpoint URL is automatically constructed based on the QuickBooks API base URL and all the path parameters.
  • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the resource data to create.
  • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a resource record. If you need to create multiple records, you can send multiple records, but each will be processed as a separate request.
  • This endpoint does not automatically create a data source to track the responses received from the QuickBooks API after each call.

  The request body must be properly formatted JSON that matches the QuickBooks API specification for creating resources. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Please check the QuickBooks API documentation for the required record structure for the resource type you want to create. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating resources, including required fields, field names, and request formats, see the QuickBooks API documentation.

  Full Update Records of a Resource

  Use this endpoint to update an existing resource. Nexset records must include all writable fields of the existing resource as returned in a read response. Fields not present are set to NULL.

  • Enter the QuickBooks Online Company ID (Realm ID) in the QuickBooks Online Company ID/ Realm ID field. This is the unique identifier of your QuickBooks company. You can get it from your Settings >> Account and settings >> Billing & Subscription page, or by clicking Control + Option + ? in your account.
  • Enter the type of resource whose records you wish to update in the Resource Type field. This should match the resource type you want to update (e.g., Customer, Account, Invoice, etc.).
  • The endpoint uses POST requests to https://quickbooks.api.intuit.com/v3/company/{realm_id}/{resource_type} where {realm_id} is the QuickBooks Online Company ID you provide and {resource_type} is the Resource Type you provide. The endpoint URL is automatically constructed based on the QuickBooks API base URL and all the path parameters.
  • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the resource data to update.
  • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to update a resource record. If you need to update multiple records, you can send multiple records, but each will be processed as a separate request.
  • This endpoint does not automatically create a data source to track the responses received from the QuickBooks API after each call.

  The request body must be properly formatted JSON that matches the QuickBooks API specification for updating resources. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Important: This is a full update operation, which means Nexset records must include all writable fields of the existing resource as returned in a read response. Fields not present in the update request are set to NULL. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about updating resources, including required fields, field names, and request formats, see the QuickBooks API documentation.

Configure Manually

Intuit QuickBooks destinations can be manually configured to send data to any valid QuickBooks API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex QuickBooks destinations, such as destinations that use custom request headers, different HTTP methods, or custom data formatting.

Content Format

1. Select the format in which the Nexset data will be sent to the QuickBooks API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The QuickBooks API typically uses JSON format for request bodies.

API Endpoint URL

2. Enter the URL of the QuickBooks API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://) and any required path parameters. QuickBooks API endpoints typically follow the pattern https://quickbooks.api.intuit.com/v3/company/{realm_id}/{endpoint_path}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The endpoint URL must include your QuickBooks Online Company ID (Realm ID) in the path. For detailed information about QuickBooks API endpoints and available APIs, see the QuickBooks API documentation.