n8n2erpnext Stock Nodes
Community n8n nodes for ERPNext/Frappe inventory movement, warehouse operations, batch and serial traceability, and ledger verification.
Inventory automation with ledger evidence
Stock is the operational center of the n8n2erpnext ecosystem because submitted stock documents change inventory balances and valuation ledgers. This node keeps movement automation close to the Bin and Stock Ledger Entry evidence that proves what happened.
Supported ERPNext resources
Item, Item Group, Warehouse, Stock Entry, Stock Reconciliation, Delivery Note, Batch, Serial No, Bin, Stock Ledger Entry, UOM, UOM Conversion Detail, Price List, Item Price, Material Request, Custom DocType, and Frappe Method. Bin and Stock Ledger Entry are intentionally read-only verification resources.
Operations and API
Writable Stock resources support Create, Get, Get Many, Update, Delete, Submit, and Cancel. Verification resources expose Get and Get Many. Both Frappe API v1 and v2 are supported. Manufacturing documents such as BOM and Work Order are reached through Custom DocType where needed.
Verified operational coverage
- Standard product lifecycle: Purchase Receipt -> inventory increase -> linked Purchase Invoice -> Sales Invoice with
update_stock = 1-> final Bin, Stock Ledger Entry, and accounting verification. - Retail and after-sales: sale -> return credit note -> warranty -> defective -> repair/virtual workshop -> disposal.
- Batch expiry, batch sale, spoilage/damage, vendor claim warehouse, basic BOM/Work Order manufacturing, and multi-company flows are covered in the workflow artifacts.
- Negative cases include over-issue, wrong warehouse, disabled item, missing warehouse, duplicate Batch/Serial, and linked-document cancellation locks.
- A standard E2E test verified purchased quantity 5, sold quantity 2, and final Bin quantity 3. The exception flow verified sellable, warranty, defective, and repair balances after disposal.
Scope
This is operational inventory validation, not enterprise MRP. Capacity planning, workstation scheduling, demand forecasting, dynamic pricing, chain-wide replenishment, and production analytics remain outside this package. Stock write workflows should run first in a dedicated test site with explicit approval and rollback review.
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.