QuickBooks Online and Marketo integration

What moves between them

Customer and vendor records from QuickBooks Online flow into Marketo. Active QuickBooks customers map to Marketo leads and companies; vendor companies map to Marketo companies. The sync runs on a schedule you define, typically daily or after key accounting periods. QuickBooks customer and vendor attributes (name, email, billing address, phone, custom fields) map to Marketo lead and company fields. Marketo is write-free in this integration - ml-connector never writes back to QuickBooks.

How ml-connector handles it

ml-connector stores both OAuth credential sets encrypted (QuickBooks realm ID and refresh token, Marketo Munchkin ID and client secret). It refreshes QuickBooks tokens when the 1-hour window closes and Marketo tokens on the same schedule, handling 401 responses by re-authenticating. Since Marketo supports polling only, ml-connector pulls QuickBooks customer and vendor records on your defined schedule and compares against the last sync state to detect new and changed records. For each new or changed QuickBooks customer, it upserts a matching Marketo lead and company record by name and email, mapping QuickBooks custom fields to Marketo lead attributes. QBO's webhook payloads omit full record details, so ml-connector polls the CDC endpoint for reliable field-level updates rather than relying on best-effort webhooks. Marketo batch limits cap each push to 300 leads or companies per request, so large customer bases are batched automatically.

A real-world example

A B2B software company uses QuickBooks Online for accounting and Marketo for lead nurturing and sales pipeline. Before the integration, the sales team manually added new customers to Marketo after contract signing, often weeks after the customer was created in accounting, leaving marketing out of the loop on pipeline velocity. With QuickBooks Online and Marketo connected, every new customer created in QuickBooks automatically flows into Marketo as a lead and company record within hours. The marketing team now runs post-sale engagement campaigns targeting new customers by industry and spend level from QuickBooks customer data, and sales can see in Marketo which accounts are active in marketing campaigns. Month-end reporting shows which marketing-touched segments actually converted to paying customers.

What you can do

• •Sync active customers and vendor companies from QuickBooks Online into Marketo as leads and companies on a schedule.
• •Map QuickBooks customer attributes (name, email, billing address, phone) to Marketo lead and company fields.
• •Refresh OAuth2 tokens automatically for both QuickBooks Online and Marketo to keep the sync reliable.
• •Detect and sync new and changed customer records from QuickBooks while respecting Marketo batch limits of 300 records per request.
• •Pull from QuickBooks CDC endpoint and customer API to ensure full record details are captured without relying on best-effort webhooks.

Questions

Which direction does data flow between QuickBooks Online and Marketo?

Data flows one direction: from QuickBooks Online into Marketo. Customers and vendors from QuickBooks become leads and companies in Marketo. Marketo remains read-only for this integration - ml-connector never writes changes back to QuickBooks. This ensures your accounting records stay authoritative and marketing changes do not alter your books.

How does ml-connector handle QuickBooks webhook limitations?

QuickBooks webhook payloads contain only entity IDs and operation type, so ml-connector does not rely on them for field-level detail. Instead, it polls the QuickBooks CDC endpoint and customer API to fetch full records with all fields. This approach is more reliable than waiting for best-effort webhooks that may arrive out-of-order or be duplicated.

What happens when OAuth tokens expire for either system?

ml-connector stores both credential sets encrypted and refreshes tokens automatically. QuickBooks access tokens expire in 1 hour, while refresh tokens rotate every 24-26 hours - ml-connector detects 401 responses and re-authenticates seamlessly. Marketo bearer tokens expire in 1 hour and are refreshed on the same schedule, so the sync never stalls due to token age.