Pipedream QuickBooks steps in n8n

QuickBooks Online workflows on Pipedream connect sales to accounting: a paid Stripe invoice creates a QuickBooks invoice and payment, a new customer in the CRM becomes a QuickBooks customer, a weekly report goes to email. n8n's native QuickBooks Online node covers the core objects. There is no trigger, which is the main design change.

The n8n QuickBooks Online node

n8n-nodes-base.quickbooks:

Resource	Operations
Bill	Create, Delete, Get, Get All, Update
Customer, Employee, Vendor	Create, Get, Get All, Update
Estimate	Create, Delete, Get, Get All, Send, Update
Invoice	Create, Delete, Get, Get All, Send, Update, Void
Payment	Create, Delete, Get, Get All, Send, Update, Void
Item, Purchase	Get, Get All
Transaction	Get Report

There is no QuickBooks trigger node.

What maps where

Pipedream (app quickbooks)	In n8n	Status
Create Customer	QuickBooks Online → Customer → Create	manual
Create Invoice	Invoice → Create (line items, customer ref)	manual
Create Payment	Payment → Create	manual
Create Bill, Create Estimate	Bill / Estimate → Create	manual
Search Invoices, Search Customers	Invoice / Customer → Get All with a query filter	manual
Create AP Aging Detail Report and other report actions	Transaction → Get Report, or HTTP Request to the reports endpoint	manual
New Invoice Created, New Customer Created, … Updated (sources)	Schedule Trigger + Get All with a MetaData.LastUpdatedTime filter, or Intuit webhook → n8n Webhook	manual

QuickBooks actions are not in the converter's automatic list; each arrives as a placeholder with the original props (customer ID, line items, amounts) so the node can be filled in directly.

Credentials

QuickBooks uses OAuth2 only:

1. In the Intuit Developer portal, create an app.
2. Under Development → Keys & OAuth, add n8n's redirect URL.
3. In n8n: Credentials → New → QuickBooks Online OAuth2, paste Client ID and Client Secret, choose Environment: Sandbox or Production.
4. Connect, then select the company.

Start in Sandbox, as n8n's docs suggest. Production keys require the app to meet Intuit's requirements, which takes time; do it before the Pipedream cutoff, not on the last day.

Typical migration: Stripe payment to QuickBooks

Pipedream: Stripe New Payment → QuickBooks Create Customer (if missing) → Create Invoice → Create Payment. n8n: Stripe Trigger (charge.succeeded or invoice.paid) → QuickBooks → Customer → Get All (by email) → If (exists?) → Customer → Create → Invoice → Create → Payment → Create.

Pitfalls

• Polling instead of instant. Pipedream's sources noticed new records for you. In n8n, a Schedule Trigger every few minutes with a "changed since last run" filter is the simple path; store the last run time in workflow static data.
• Line items. Invoices need item references (ItemRef) that exist in QuickBooks; copy IDs, not names.
• Sandbox data. Sandbox companies are separate; IDs differ from production. Re-map IDs after switching the credential.
• Taxes and currencies depend on company settings (US vs non-US editions). Test one invoice end to end before bulk runs.
• Rate limits. Intuit throttles per company and app; spread bulk imports with a Wait node. Check Intuit's current limits in its developer docs.

How to move your QuickBooks workflows

1. Export the workflows from Pipedream.
2. Upload on /convert; the free report lists the QuickBooks steps and the manual triggers.
3. Download the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide and the code step checker for code using node-quickbooks. Related: Stripe, Shopify, Salesforce.