Block 1 - Sticky Note5
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
AI Invoice Processor for QuickBooks Email to Bill with PDF Attachment Automatically processes vendor invoices received by email, creates QuickBooks bills with full details, and attaches the origina...
n8n-nodes-base.stickynote, n8n-nodes-base.gmailtrigger, n8n-nodes-base.set, n8n-nodes-base.extractfromfile, @n8n/n8n-nodes-langchain.informationextractor, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.if, n8n-nodes-base.code
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Codez & AI.
Original n8n.io sourceAutomatically processes vendor invoices received by email, creates QuickBooks bills with full details, and attaches the original PDF.
realmId - your QuickBooks Company ID (Settings → Account)apTeamEmail - where error notifications godefaultExpenseAccountId - your QB expense account ID (see below)accountId=XX or account=XXdefaultExpenseAccountIdIf using QuickBooks Sandbox, update the Upload PDF to Bill node URL from:
https://quickbooks.api.intuit.com/v3/company/...
to:
https://sandbox-quickbooks.api.intuit.com/v3/company/...
The AI extracts these fields from each invoice PDF:
| Field | Type | Example |
|---|---|---|
is_invoice |
boolean | true |
vendor_name |
string | "Acme Corp" |
invoice_number |
string | "INV-2024-001" |
amount |
number | 1500.00 |
currency |
string | "USD" |
due_date |
string | "2024-12-31" |
txn_date |
string | "2024-12-01" |
line_items |
array | [{description, amount, quantity}] |
PDF binary data is lost after the AI extraction step (LangChain nodes don't preserve binary). The attachment pipeline solves this by referencing the binary from the Config node using $('Config').item.binary.attachment_0 - a named reference that works regardless of the connection path.
n8n v2 stores binary data as database streams. QuickBooks' /upload API requires Content-Length in multipart uploads, which streams can't provide. A Code node converts binary streams to inline base64 before upload.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 28 workflow blocks. Download the JSON for the full node graph.
| Workflow | Process emailed PDF invoices into QuickBooks bills with OpenAI |
|---|---|
| Complexity | advanced |
| Nodes | 28 |
| Categories | Invoice Processing, AI Summarization |
| Author | Codez & AI |
| Published | 16 Mar 2026 |
Use the JSON export at /data/workflows/14085/14085.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
AI Invoice Processor for QuickBooks Email to Bill with PDF Attachment Automatically processes vendor invoices received by email, creates QuickBooks bills with full details, and attaches the origina...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Invoice Processing, AI Summarization use case.