For the complete documentation index, see llms.txt. This page is also available as Markdown.

Quickbooks Customers

Downloads all QuickBooks customer records into Labii and synchronizes account and contact information for consistent CRM and billing workflows.

Specs

Label
Value

Version

1.0.0 (updated on 2026-07-12)

Developer

Labii Inc.

Type

Dashboard

Support Configuration

Yes

Overview

The Quickbooks Customers widget imports customer data from QuickBooks Online into Labii and keeps existing records synchronized. It organizes downloaded customer information into two linked data areas, including company-level account records and person-level contact records. This widget helps teams centralize customer master data, reduce manual entry, and improve consistency across finance and operational processes.

Use Cases

  • Bulk Customer Import: Download all QuickBooks customers into Labii in one run.

  • Account and Contact Sync: Keep company and contact records aligned with QuickBooks updates.

  • CRM Data Readiness: Prepare customer data for invoicing, communication, and account management workflows.

  • Cross-System Consistency: Maintain shared identifiers for reliable downstream integrations.

Configuration

Initial Setup

1

Navigate to the dashboard where you want to add the widget.

2

Click Add Widget and select Quickbooks Customers from the dashboard widget catalog.

3

Configure required authorization, project assignment, and table-to-column mappings for account and contact data.

4

Click Save to add the widget to your dashboard.

Required Settings

  • Realm ID: Unique identifier for your QuickBooks Online company.

  • Refresh Token: OAuth refresh token used to authenticate and retrieve customer data.

  • Is Sandbox: Enable when connecting to QuickBooks sandbox instead of production.

  • Projects: Project(s) to associate with synchronized accounts and contacts.

  • Account Table: Table that stores account-level customer data.

  • Account: QuickBooks Customer ID Column: Column for QuickBooks customer ID.

  • Account: QuickBooks Sync Token Column: Column for QuickBooks sync token.

  • Account: Billing Address Column: Column for billing address data.

  • Account: Shipping Address Column: Column for shipping address data.

  • Account: Point of Contact Column: Column for account-level primary contact reference.

  • Contact Table: Table that stores contact-level customer data.

  • Contact: Account Column: Column linking contact to account.

  • Contact: Title Column: Column for contact title.

  • Contact: Email Column: Column for contact email.

  • Contact: Office Phone Column: Column for office phone.

  • Contact: Cell Phone Column: Column for cell phone.

Optional Settings

  • Project Scope Selection: Limit synchronization to selected project contexts.

  • Sandbox Mode: Use for testing mappings before production data sync.

Run initial synchronization in sandbox mode to validate account-contact relationships before production import.

Readonly View

Dashboard widgets are displayed in read-only mode on dashboards for monitoring and actions.

Display Features

  • Start Download Button: Triggers customer download and synchronization.

  • Status Feedback: Indicates sync progress and completion status.

  • Mapped Destinations: Uses configured account and contact tables for writes.

Interactive Features

  • Start Download: Manually run customer synchronization.

  • Re-run Sync: Repeat download to update existing customer records.

Additional Functions

Download and Synchronize

After configuration is complete, click Start Download to import customer data from QuickBooks. Existing Labii records are updated when matching identifiers are found.

Dual-Table Data Organization

  • Splits imported data into account and contact structures for better data management.

  • Preserves linkage between customer accounts and associated contacts.

Best Practices

  • Validate both account and contact mappings in sandbox before production sync.

  • Keep QuickBooks customer ID and sync token columns immutable to prevent duplicates.

  • Ensure account-contact relationship columns are correctly configured before first run.

  • Perform periodic re-sync to keep customer communication data current.

Last updated