Open-source engineering for ERPNext/Frappe operations, Vietnam localization, evidence-governed BI, secure AI-to-machine connectivity, and self-hosted automation.
Built from real operational workflows, with explicit boundaries, auditable evidence, and production-minded deployment patterns.

n8n2erpnext has grown beyond its original n8n node packages. The organization now hosts a small open-source stack around ERPNext/Frappe operations, Vietnamese localization, business analysis, AI-to-machine connectivity, edge integration, and zero-trust infrastructure.

The original project family remains active as modular community nodes rather than a single monolithic connector:

The repositories are different products, but they share the same engineering posture:

• Preserve upstream boundaries. Prefer Frappe/ERPNext extension points, companion apps, adapters, and explicit contracts over unnecessary core forks.
• Fail closed when evidence is weak. LightBI does not speculate joins or silently substitute measures when source identity, grain, or analytical authorization is uncertain.
• Version rules that change over time. ERPNext Vietnam keeps legal rules effective-dated and auditable, with preview/apply separation and certification gates for external transports.
• Govern remote execution at the device boundary. Light Remote MCP uses explicit node targeting, signed outbound device channels, local capability re-inference, and no silent fallback to another machine.
• Make risky infrastructure changes reviewable. Zero Trust Syncd defaults to preview/dry-run patterns, explicit guardrails, drift detection, snapshots, and documented failure behavior.
• Keep the edge resilient. Edge Attendance Gateway validates requests locally, queues durably when upstream ERPNext is unavailable, and synchronizes only across an explicit trust boundary.
• Treat localization as domain work. erpnext2vi translates for business meaning and runtime context across ERP, HRMS, CRM, Healthcare, Hospitality, and other Frappe applications instead of word-for-word substitution.
• Self-host where it improves control. Local-first execution, operator diagnostics, upgradeability, privacy boundaries, and recoverability are treated as product features rather than deployment afterthoughts.

The n8n package family is the organization's original ERP automation layer. It provides open-source community nodes for ERPNext and Frappe and helps teams automate real operations such as accounting, procurement, sales, warehouse movement, inventory validation, and cross-module document integrity.

The project is designed for:

• ERPNext automation with n8n.
• Frappe REST API integrations.
• Self-hosted ERP operations.
• SME and mid-market business workflow automation.
• Retail, distribution, stock, buying, selling, accounting, HRMS, and ERP operations.
• AI-searchable ERPNext integration examples with production-style README documentation.

The core business modules are now validated as one connected ERP system:

Buying -> Stock -> Selling -> Accounting

The Stock validation suite includes two live-tested enterprise workflows that prove cross-module behavior end to end:

Standard Product Lifecycle
Supplier -> Purchase Receipt -> Inventory Increase -> Purchase Invoice
-> Customer Sale -> Sales Invoice update_stock=1 -> Inventory Decrease
-> Bin, Stock Ledger Entry, and Accounting verification

Exception / After-Sales Lifecycle
Sale -> Return Credit Note -> Warranty Warehouse -> Defective Warehouse
-> Repair / Virtual Workshop -> Disposal
-> Bin, Stock Ledger Entry, and Accounting verification

These workflows prove:

• Inventory can safely enter the business.
• Inventory can safely move through warehouses.
• Inventory can safely leave through sales.
• Return, warranty, defect, repair, and disposal flows are covered.
• Internal trade can move stock and accounting across two ERPNext companies.
• Purchase Invoice locks protect Purchase Receipt cancellation.
• Sales Invoice locks protect Delivery Note cancellation.
• Linked inter-company Purchase Invoice records protect Sales Invoice cancellation.
• Valid inter-company reversal works when the receiving Purchase Invoice is cancelled before the source Sales Invoice.
• Non-stock fee and rebate invoices do not create Stock Ledger Entry rows.
• Public webhook responses are allowlisted and checked for credential leaks.

Detailed coverage notes, tested ERPNext pain points, and live document references are maintained in docs/ecosystem-coverage.md.

Module	Package	npm	Scope	Status
Core	n8n-nodes-frappe-core	Foundation package	Generic Frappe API, shared credential pattern, core API behavior	In progress
HRMS	n8n-nodes-erpnext-hrms	npm	Employees, attendance, leave, payroll-adjacent workflows	Live
Accounting	n8n-nodes-erpnext-accounting	npm	Sales Invoice, Purchase Invoice, Payment Entry, Journal Entry, GL Entry	Live
Buying	n8n-nodes-erpnext-buying	npm	Supplier, RFQ, Supplier Quotation, Purchase Order, Purchase Receipt	Live
Selling	n8n-nodes-erpnext-selling	npm	Customer, Lead, Opportunity, Quotation, Sales Order	Live
Stock	n8n-nodes-erpnext-stock	npm	Item, Warehouse, Stock Entry, Delivery Note, Batch, Serial No, Bin, Stock Ledger Entry	Live

The active ecosystem has been tested against ERPNext/Frappe v16 behavior on a self-hosted n8n runtime with API v1 and API v2 document workflows.

Many ERPNext integrations stop at generic HTTP requests. n8n2erpnext goes further by packaging repeatable, module-aware n8n nodes with:

• ERPNext-specific resources and operations.
• Frappe API v1 and v2 support.
• Submit and cancel helper behavior.
• Read-only ledger verification resources where safety matters.
• Importable workflow artifacts for real ERP validation.
• Production security notes for credentials, webhooks, and response design.
• Cross-module workflows that mirror actual business operations.

In n8n, install the package you need from the Community Nodes interface:

n8n-nodes-erpnext-accounting
n8n-nodes-erpnext-buying
n8n-nodes-erpnext-selling
n8n-nodes-erpnext-stock
n8n-nodes-erpnext-hrms

For manual installation in a custom n8n nodes environment:

npm install n8n-nodes-erpnext-stock
npm install n8n-nodes-erpnext-accounting
npm install n8n-nodes-erpnext-buying
npm install n8n-nodes-erpnext-selling

All module packages use the shared ERPNext API credential pattern:

Site URL: https://erp.example.com
Site Host Header: erp.example.com
API Key: your ERPNext API key
API Secret: your ERPNext API secret
Ignore SSL Issues: false

For private VPS or container deployments, n8n can call ERPNext through an internal URL while still sending the public Frappe site host header:

Site URL: http://erpnext.internal:8001
Site Host Header: erp.example.com

The project favors operational safety over broad, unchecked API exposure:

• Use dedicated ERPNext API users.
• Scope roles to the exact DocTypes used by each workflow.
• Prefer explicit fields for public webhook responses.
• Treat Stock and Accounting workflows as high-impact operations.
• Deactivate temporary write-test workflows after verification.
• Do not expose generic Custom DocType or Frappe Method workflows publicly.
• Use VPN, reverse proxy auth, header auth, IP allowlists, or shared secrets for public webhooks.
• Reduce saved n8n execution data for workflows that process financial, inventory, payroll, or customer records.

ERPNext n8n integration, Frappe n8n nodes, n8n community nodes ERPNext, ERPNext automation, Frappe automation, ERPNext Accounting n8n, ERPNext Buying n8n, ERPNext Selling n8n, ERPNext Stock n8n, ERPNext HRMS n8n, ERPNext API v2 n8n, Frappe REST API n8n, ERPNext workflow automation, n8n ERP integration, self-hosted ERPNext automation, warehouse automation ERPNext, stock ledger ERPNext n8n, purchase receipt ERPNext n8n, sales invoice ERPNext n8n, business lifecycle ERPNext automation.

Planned direction:

• Keep module READMEs concise and production-focused.
• Add focused workflow documentation for retail, manufacturing basics, FMCG/Fresh, multi-company, and coverage matrices.
• Keep V1 focused on maintenance, issue response, documentation fixes, and dependency/security updates.
• Build Core V2 only when enough real issues and custom ERPNext examples arrive.
• Position Core V2 as a Frappe/ERPNext Customization Bridge: Custom DocTypes, custom fields, dynamic metadata, child tables, method helpers, and schema translation for real ERPNext/Frappe customization pain points.
• Add additional modules only when they can follow the same live-tested standard.
• Expand automated tests for request construction, endpoint selection, and credential redaction.
• Keep the ecosystem modular so teams can install only the ERPNext domain they need.

• ERPNext
• Frappe Framework
• Frappe REST API
• n8n Community Nodes
• n8n Creating Nodes

Each package is released under its repository license. Core module packages are MIT unless noted otherwise in the package repository.