QuickBooks Invoice PDF Archiving to Google Drive - n8n Workflow

Finance and Accounting Teams: Users who need reliable, automatic archiving of every generated invoice for audit purposes.
Bookkeepers and CPAs: Professionals managing multiple client accounts who require centralized document storage.
n8n Automation Users: Developers and users looking for robust n8n templates to handle cloud file operations triggered by financial events.
QuickBooks Power Users: Individuals seeking to extend QuickBooks' functionality using a powerful n8n node integration.

Manually downloading and storing invoice PDFs from QuickBooks is a repetitive and error-prone task. This high-efficiency n8n workflow template solves this by providing a seamless, automated archival pipeline. Utilizing a webhook n8n trigger, the process begins the moment an invoice is created or updated in QuickBooks. The n8n workflow instantly fetches the necessary data, generates the official QuickBooks PDF document using an HTTP Request n8n node, and saves it to a designated folder in Google Drive. This ensures that your financial records are always up-to-date, securely stored, and instantly accessible, drastically improving compliance and operational efficiency. This specific n8n workflow is a prime example of real-time data synchronization.

This automation operates in four logical steps, triggered instantly by an external event:

1. QuickBooks Webhook n8n Trigger: The workflow starts when the QuickBooks Webhook receives a POST request indicating that a new invoice event has occurred. This specialized n8n trigger provides the immediate notification needed for real-time processing.


2. Fetch Invoice Details: The QuickBooks n8n node uses the invoice ID provided by the webhook payload to retrieve all detailed invoice information (customer name, date, amounts) necessary for naming the archival file.


3. Generate PDF File: An HTTP Request n8n node connects back to the QuickBooks API. It uses OAuth2 authentication and requests the PDF endpoint for the specific invoice ID. By setting the Accept header to application/pdf, it forces QuickBooks to return the binary PDF file data, which is crucial for the subsequent upload step in this n8n workflow.


4. Upload to Google Drive: Finally, the Google Drive n8n node takes the binary file output from the previous step. It uses an expression to dynamically name the file (e.g., CustomerName_Date.pdf) and uploads it directly to the predefined Google Drive folder, completing the n8n workflow cycle.

To deploy this n8n workflow and start automating your document archiving, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON data and import it directly into your n8n instance.


2. Configure Credentials: Establish and connect two sets of credentials:

1. Set Up the Webhook:

1. Configure Google Drive Node:

1. Activate: Set the n8n workflow to 'Active' to start listening for real-time QuickBooks events.

This n8n workflow relies on key configuration within the following n8n node types:

QuickBooks Webhook (n8n trigger):
Function: Starts the n8n workflow upon receiving an invoice creation/update event from QuickBooks.
Key Configuration: Path set to /quickbooks-invoice; Method set to POST.
QuickBooks (Get an invoice):
Function: Fetches the full dataset of the invoice using the ID passed by the webhook n8n trigger.
Key Configuration: Invoice ID uses the expression {{ $json.body.eventNotifications[0].dataChangeEvent.entities[0].id }}.
Generate PDF File (HTTP Request n8n node):
Function: Generates the binary PDF file directly from the QuickBooks API.
Key Configuration: Uses predefined QuickBooks OAuth2 credentials; URL is dynamically constructed with Realm ID and Invoice ID; Header Parameter includes Accept: application/pdf to ensure binary file output.
Upload file (Google Drive n8n node):
Function: Archives the binary PDF file output to Google Drive.
Key Configuration: Folder ID is set to the target archival folder; Name uses the expression ={{ $json["CustomerRef"]["name"] + "_" + $json["TxnDate"] + ".pdf" }} for unique, readable filenames.