QUICKBOOKS n8n INTEGRATION: AUTOMATE QUICKBOOKS WITH N8N

The Update Vendor action allows you to modify existing vendor records in your QuickBooks account directly from your n8n workflows. This is essential for keeping supplier information current when details change in other systems—whether that's updated contact information from your procurement platform or revised payment terms from your vendor management system.

Key parameters: Credential to connect with (dropdown to select your QuickBooks Online account connection, required); Vendor ID (text field where you specify the unique identifier of the vendor you want to update, required); Update Fields (dynamic section where you add specific properties to modify—click "Add Field" to reveal available vendor properties like display name, company name, contact information, address details, and payment terms).

Use cases: Sync vendor address changes from your supplier portal to QuickBooks; update payment terms automatically when contracts are renegotiated; modify vendor contact information when notified of personnel changes.

This action retrieves multiple vendor records from QuickBooks, perfect for building reports, populating dashboards, or syncing vendor data to other systems. You can fetch all vendors or limit results to a specific number, and apply filters to narrow down the records returned.

Key parameters: Resource (set to "Vendor" to work with vendor records, required); Operation (set to "Get Many" for retrieving multiple records, required); Return All (toggle switch—enable to retrieve all vendors regardless of limit, optional); Limit (number field specifying maximum records to return, default 50, active when Return All is disabled, optional); Filters (add filtering conditions to narrow results by specific vendor properties, optional).

Use cases: Export vendor lists for procurement team reviews; populate vendor selection dropdowns in custom applications; compare vendor records against external supplier databases for discrepancies.

Retrieve detailed information for a single, specific vendor using their unique QuickBooks ID. This action is ideal when you need complete vendor data for processing in subsequent workflow steps or when responding to specific vendor-related events.

Key parameters: Vendor ID (text input for the unique identifier of the vendor to retrieve, required for single-record retrieval).

Use cases: Fetch vendor payment details before processing a bill payment; retrieve vendor contact information for automated email notifications; pull complete vendor records for data validation workflows.

Create new vendor records in QuickBooks directly from your automation workflows. This action streamlines supplier onboarding by automatically adding vendors when they're approved in your procurement system or when new supplier agreements are signed.

Key parameters: Display Name (text field for the vendor's display name in QuickBooks, optional but recommended for identification); Additional Fields (expandable section to add contact information, addresses, payment terms, tax identifiers, and other vendor properties).

Use cases: Automatically create vendors when new suppliers are approved in your procurement workflow; sync new supplier records from your ERP system to QuickBooks; onboard freelancers and contractors as vendors when contracts are signed.

Generate transaction reports directly from QuickBooks, providing valuable financial insights for analysis, compliance, or executive reporting. This action retrieves transaction data in a structured format that's easy to process in subsequent workflow steps.

Key parameters: Resource (set to "Transaction" for transaction-related data, required); Operation (set to "Get Report" to retrieve report data, required); Simplify (toggle to streamline the output structure for easier processing—when enabled, the response is formatted more cleanly, optional); Filters (add date ranges, transaction types, or other criteria to refine your report, optional).

Use cases: Generate weekly financial summaries and post to Slack or email; pull transaction data for custom dashboard visualizations; create compliance reports for specific date ranges automatically.

Retrieve multiple purchase records from QuickBooks for analysis, reconciliation, or synchronization with other systems. This action is valuable for expense tracking workflows and financial reporting.

Key parameters: Resource (set to "Purchase" for purchase records, required); Return All (toggle to fetch all purchase records, optional); Limit (maximum number of purchase records to return, default 50, optional); Filters (add criteria to filter purchases by specific properties, optional).

Use cases: Export purchase history for expense analysis; reconcile purchases against credit card statements; generate spending reports by vendor or category.

Retrieve detailed information for a specific purchase record using its unique QuickBooks ID. Essential for workflows that need to process or validate individual purchase transactions.

Key parameters: Purchase ID (text field for the unique identifier of the purchase to retrieve, required).

Use cases: Fetch purchase details for approval workflows; retrieve receipt information for expense categorization; pull purchase data for audit trails.

Void an existing payment record in QuickBooks. This action is useful for handling payment reversals, corrections, or refund scenarios where the original payment needs to be nullified.

Key parameters: Resource (set to "Payment" to work with payment records, required); Operation (set to "Void" to nullify the payment, required); Payment ID (unique identifier of the payment to void, required).

Use cases: Automatically void payments when refunds are processed in your e-commerce platform; handle payment corrections when errors are detected; process chargebacks by voiding the original payment record.

Modify existing payment records in QuickBooks to correct information or add details. This action helps maintain accurate payment histories when changes are needed after initial recording.

Key parameters: Payment ID (unique identifier of the payment to update, required); Update Fields (dynamic section for specifying which payment properties to modify—click "Add Field" to select from available options like payment method, amount, or memo).

Use cases: Update payment memos with additional transaction details; correct payment method information after processing; add reference numbers from external payment processors.

Send payment receipt notifications to customers directly from QuickBooks. This action automates customer communication by emailing payment confirmations when payments are recorded.

Key parameters: Payment ID (unique identifier of the payment to send, required); Email (email address where the payment receipt will be sent, required).

Use cases: Automatically email payment receipts when payments are processed; send payment confirmations to customers after subscription renewals; notify clients when retainer payments are received.

Retrieve multiple payment records from QuickBooks for reporting, reconciliation, or analysis. This action provides a comprehensive view of payment activity.

Key parameters: Return All (toggle to fetch all payment records, optional); Limit (maximum payments to return when Return All is disabled, default 50, optional); Filters (add criteria to filter payments by date, customer, or other properties, optional).

Use cases: Generate daily payment reports for accounting team; export payment data for cash flow analysis; reconcile payments against bank deposits.

Retrieve complete details for a specific payment record. Includes an option to download associated files or attachments.

Key parameters: Payment ID (unique identifier of the payment to retrieve, required); Download (toggle to download associated files with the payment data, optional).

Use cases: Fetch payment details for customer service inquiries; retrieve payment information for accounting reconciliation; pull payment records with receipts for audit purposes.

Remove a payment record from QuickBooks. Use this action carefully, as deleted payments cannot be recovered—voiding is often preferred for maintaining audit trails.

Key parameters: Payment ID (unique identifier of the payment to delete, required).

Use cases: Clean up duplicate payment entries; remove test payments from production accounts; delete erroneously created payment records.

Record new payments in QuickBooks when customers pay invoices. This action is essential for maintaining accurate accounts receivable and customer balances.

Key parameters: For Customer Name or ID (customer associated with the payment—uses search/dropdown to select from your QuickBooks customers, required); Total Amount (payment amount to record, required); Additional Fields (add payment method, deposit account, reference number, and other payment details, optional).

Use cases: Automatically record payments when processed through Stripe or PayPal; create payment records when customers pay via bank transfer; log cash payments recorded in POS systems.

Retrieve multiple inventory or service items from QuickBooks. Essential for product catalog management, inventory sync, and pricing workflows.

Key parameters: Resource (set to "Item" for product/service items, required); Return All (toggle to fetch all items, optional); Limit (maximum items to return, default 50, optional); Filters (add criteria to filter items by type, status, or other properties, optional).

Use cases: Sync product catalogs to e-commerce platforms; export item lists for inventory management systems; generate pricing reports for sales teams.

Retrieve detailed information for a specific item using its unique ID. Perfect for workflows that need to reference product details, pricing, or inventory levels.

Key parameters: Item ID (unique identifier of the item to retrieve, required).

Use cases: Fetch current pricing before generating quotes; retrieve item details for order processing; pull inventory information for stock alerts.

Void an existing invoice in QuickBooks. This nullifies the invoice while maintaining the record for audit purposes—preferred over deletion in most scenarios.

Key parameters: Resource (set to "Invoice" for invoice records, required); Operation (set to "Void" to nullify the invoice, required); Invoice ID (unique identifier of the invoice to void, required).

Use cases: Void invoices when orders are cancelled; handle invoice corrections by voiding and recreating; process refunds that require invoice reversal.

Modify existing invoices in QuickBooks to correct information, add line items, or update terms. Maintains the original invoice while applying necessary changes.

Key parameters: Invoice ID (unique identifier of the invoice to update, required); Update Fields (dynamic section for specifying modifications—add fields for due date, line items, memo, customer message, or other invoice properties).

Use cases: Adjust invoice amounts when pricing errors are discovered; update due dates for payment term extensions; add late fees or credits to existing invoices.

Email invoices to customers directly from QuickBooks. This action automates invoice delivery, ensuring customers receive bills promptly when they're created or updated.

Key parameters: Invoice ID (unique identifier of the invoice to send, required); Email (recipient email address for the invoice, required).

Use cases: Automatically email invoices when they're created; resend invoices when customers report non-receipt; send reminder emails for overdue invoices.

Retrieve multiple invoices from QuickBooks for reporting, aging analysis, or bulk operations. Filter by date, status, or customer to get exactly the records you need.

Key parameters: Return All (toggle to fetch all invoices, optional); Limit (maximum invoices to return, default 50, optional); Filters (add criteria like date range, customer, or status to narrow results, optional).

Use cases: Generate accounts receivable aging reports; export invoices for external accounting review; create overdue invoice notification workflows.

Retrieve complete details for a specific invoice, including line items, customer information, and payment status. Optionally download the invoice as a document.

Key parameters: Invoice ID (unique identifier of the invoice to retrieve, required); Download (toggle to download the invoice as a PDF, optional).

Use cases: Fetch invoice details for customer support inquiries; retrieve invoices for payment matching workflows; download invoice PDFs for record keeping.

Permanently remove an invoice from QuickBooks. This action should be used sparingly—voiding is typically preferred for maintaining complete financial records.

Key parameters: Invoice ID (unique identifier of the invoice to delete, required).

Use cases: Remove duplicate invoices created in error; clean up test invoices from production; delete draft invoices that were never finalized.

Create new invoices in QuickBooks with full control over customer, line items, and additional details. This is one of the most commonly used actions for accounts receivable automation.

Key parameters: For Customer Name or ID (customer to invoice—select from your QuickBooks customer list, required); Line (add individual line items with product/service, quantity, rate, and amount—click "Add item" for each line); Additional Fields (include invoice number, due date, terms, memo, shipping address, and other invoice details, optional).

Use cases: Automatically create invoices when projects are completed; generate invoices from approved timesheets; create recurring invoices for subscription services.

Modify existing estimates to reflect changes in scope, pricing, or terms. Keeps quote information current throughout the sales process.

Key parameters: Estimate ID (unique identifier of the estimate to update, required); Update Fields (dynamic section for specifying changes to estimate properties, line items, or terms).

Use cases: Update estimates when project scope changes; adjust pricing before final customer approval; add or remove line items during negotiation.

Email estimates to customers or prospects for review and approval. Streamlines the quoting process by automating delivery.

Key parameters: Estimate ID (unique identifier of the estimate to send, required); Email (recipient email address for the estimate, required).

Use cases: Send estimates immediately after creation; resend estimates with updated pricing; automate follow-up emails for pending estimates.

Retrieve multiple estimates for pipeline analysis, conversion tracking, or reporting purposes. Filter by status to focus on active quotes.

Key parameters: Return All (toggle to fetch all estimates, optional); Limit (maximum estimates to return, default 50, optional); Filters (add criteria to filter by status, customer, or date, optional).

Use cases: Generate quote-to-close conversion reports; track pending estimates for sales pipeline; export estimate history for analysis.

Retrieve complete details for a specific estimate, including all line items and terms. Optionally download as a document.

Key parameters: Estimate ID (unique identifier of the estimate to retrieve, required); Download (toggle to download the estimate as a PDF, optional).

Use cases: Fetch estimate details for approval workflows; retrieve estimates for comparison or analysis; download estimate PDFs for customer meetings.

Permanently remove an estimate from QuickBooks. Best used for cleaning up draft or duplicate estimates.

Key parameters: Estimate ID (unique identifier of the estimate to delete, required).

Use cases: Remove duplicate estimates created in error; clean up old draft quotes; delete test estimates from production accounts.

Create new estimates for customers, complete with line items, terms, and custom messaging. Essential for automating the quoting process.

Key parameters: For Customer Name or ID (customer to quote—select from your QuickBooks customer list, required); Line (add individual line items with products/services and pricing—click "Add item" for each line); Additional Fields (include expiration date, memo, customer message, and other estimate details, optional).

Use cases: Generate estimates automatically from CRM opportunities; create quotes when quote requests are submitted via forms; produce estimates from configured product bundles.

Modify existing employee records in QuickBooks to keep personnel information current. Useful for HR system integrations.

Key parameters: Employee ID (unique identifier of the employee to update, required); Update Fields (dynamic section for specifying which employee properties to modify—name, contact info, address, etc.).

Use cases: Sync employee address changes from HR systems; update contact information when employees notify changes; modify employee status or department assignments.

Retrieve multiple employee records for reporting, directory creation, or synchronization with other HR systems.

Key parameters: Return All (toggle to fetch all employees, optional); Limit (maximum employees to return, default 50, optional); Filters (add criteria to filter employees by specific properties, optional).

Use cases: Export employee lists for payroll processing; generate company directories; sync employee data to HR management platforms.

Retrieve complete information for a specific employee using their unique QuickBooks ID.

Key parameters: Employee ID (unique identifier of the employee to retrieve, required).

Use cases: Fetch employee details for onboarding workflows; retrieve contact information for notifications; pull employee records for verification processes.

Add new employee records to QuickBooks when hires are made. Streamlines onboarding by automatically creating employee profiles.

Key parameters: Family Name (employee's last name, optional); Given Name (employee's first name, optional); Additional Fields (add contact information, addresses, hire date, and other employee properties, optional).

Use cases: Automatically create employees when new hires are added in HR systems; onboard contractors with basic employee records; sync new employee data from recruiting platforms.

Modify existing customer records to keep contact information, payment terms, and other details current.

Key parameters: Customer ID (unique identifier of the customer to update, required); Update Fields (dynamic section for specifying customer properties to modify—display name, contact info, billing address, etc.).

Use cases: Sync customer updates from CRM systems; update billing addresses when customers relocate; modify payment terms based on customer relationships.

Retrieve multiple customer records for analysis, export, or synchronization. Filter by status or other criteria as needed.

Key parameters: Return All (toggle to fetch all customers, optional); Limit (maximum customers to return, default 50, optional); Filters (add criteria to narrow customer results, optional).

Use cases: Export customer lists for marketing campaigns; sync customers to CRM or email marketing platforms; generate customer reports for sales team.

Retrieve complete information for a specific customer using their unique QuickBooks ID.

Key parameters: Customer ID (unique identifier of the customer to retrieve, required).

Use cases: Fetch customer details for personalized communications; retrieve billing information for payment processing; pull customer data for order fulfillment.

Add new customer records to QuickBooks when customers are acquired. Essential for maintaining accurate customer databases across systems.

Key parameters: Display Name (customer name as it will appear in QuickBooks, required); Additional Fields (add contact information, billing/shipping addresses, payment terms, tax info, and more, optional).

Use cases: Automatically create customers when deals close in CRM; add customers when they complete registration forms; sync new customers from e-commerce platforms.

Modify existing vendor bills to correct amounts, add details, or update due dates.

Key parameters: Bill ID (unique identifier of the bill to update, required); Update Fields (dynamic section for specifying which bill properties to modify).

Use cases: Update bill amounts when receiving corrected invoices from vendors; adjust due dates based on payment negotiations; add reference numbers or memos for tracking.

Retrieve multiple bills for accounts payable reporting, aging analysis, or payment scheduling.

Key parameters: Return All (toggle to fetch all bills, optional); Limit (maximum bills to return, default 50, optional); Filters (add criteria to filter bills by vendor, status, or date, optional).

Use cases: Generate accounts payable aging reports; export bills for payment batch processing; track outstanding bills by vendor.

Retrieve complete details for a specific bill using its unique QuickBooks ID.

Key parameters: Bill ID (unique identifier of the bill to retrieve, required).

Use cases: Fetch bill details for approval workflows; retrieve vendor invoice information for payment processing; pull bill data for expense categorization.

Permanently remove a bill from QuickBooks. Use carefully—this action cannot be undone.

Key parameters: Bill ID (unique identifier of the bill to delete, required).

Use cases: Remove duplicate bills created in error; delete test bills from production accounts; clean up draft bills that were never finalized.

Create new vendor bills in QuickBooks when invoices are received from suppliers. Streamlines accounts payable by automating bill entry.

Key parameters: For Vendor Name or ID (vendor who issued the bill—select from your QuickBooks vendor list, required); Line (add individual line items with expense categories and amounts—click "Add item" for each line); Additional Fields (include bill number, due date, memo, and other bill details, optional).

Use cases: Automatically create bills when vendor invoices arrive via email; generate bills from approved purchase orders; sync vendor invoices from procurement systems.