n8n2erpnext Buying Nodes
Community n8n nodes for ERPNext/Frappe procurement workflows from suppliers and RFQs through purchase orders, receipts, and accounting handoff.
Procurement workflows from supplier to receipt
The Buying node provides a controlled n8n boundary for supplier and procurement operations. It covers the path from a supplier request through quotation, purchase order, receipt, and the accounting documents that follow.
Supported ERPNext resources
Supplier, Supplier Quotation, Request for Quotation, Purchase Order, Purchase Receipt, Material Request, Item, Contact, Address, Custom DocType, and Frappe Method.
Operations and API
Buying resources support Create, Get, Get Many, Update, Delete, Submit, and Cancel through Frappe API v1 or v2. The shared helper fetches the latest document before submit/cancel and applies the correct Frappe method payload. Adjacent documents such as Purchase Invoice and Payment Entry use Custom DocType deliberately.
Verified procurement flows
- Read-only supplier retrieval returned HTTP 200 with an allowlisted field set.
- The real procurement flow covered Vietnamese and special-character supplier names, disabled-supplier readback, multi-item requests, RFQ submit/cancel, Supplier Quotation, discounted Purchase Order, partial Purchase Receipt, Purchase Invoice, partial payment cancel, and full payment.
- ERPNext database readback verified submitted documents, stock ledger rows, invoice payment status, and amended Purchase Order behavior.
- Negative cases correctly rejected duplicate Supplier creation, missing required Supplier, cancellation of a linked order, deletion of a submitted receipt, and fake document lookup.
Scope
Buying is procurement-focused. Put mostly financial workflows in Accounting and use Custom DocType only for intentional cross-module boundaries. Write-heavy workflows are shipped as inactive artifacts and should be tested in a dedicated site first.
Integration and security boundary
The node authenticates to Frappe with an ERPNext API credential and supports an internal URL plus Site Host Header for self-hosted deployments. Use a dedicated integration user with scoped roles, explicit fields for read workflows, private or authenticated webhooks, HTTPS, and controlled execution-data retention. Never expose API keys, secrets, authorization headers, raw upstream errors, or full ERPNext documents through a public workflow.
Build and release
Each package is released as an MIT-licensed n8n community node with TypeScript build/lint checks, n8n node-cli validation, npm audit, and packed-artifact review. Install the package from npm or inspect the source at GitHub. Temporary write-test workflows are deactivated after verification.