n8n2erpnext Selling Nodes
Community n8n nodes for ERPNext/Frappe sales workflows covering customers, leads, opportunities, quotations, sales orders, revenue, and controlled cross-module bridges.
Sales workflows from lead to payment
The Selling node connects customer-facing ERPNext documents to n8n. It supports a practical commercial path from customer and lead records through opportunity, quotation, sales order, invoice, and payment bridges.
Supported ERPNext resources
Customer, Lead, Opportunity, Quotation, Sales Order, Sales Partner, Sales Person, Item, Contact, Address, Custom DocType, and Frappe Method.
Operations and API
Selling resources support Create, Get, Get Many, Update, Delete, Submit, and Cancel using Frappe API v1 or v2. Delivery Note, Sales Invoice, and Payment Entry are reached through explicit Custom DocType bridges. Sales Order amendment follows ERPNext's cancel -> amended_from -> submit lifecycle.
Verified sales flows
- Customer read webhook returned HTTP 200 with explicit fields and no credential material.
- The real sales flow covered Customer, disabled Customer, Lead, Item, Opportunity, submitted Quotation, submitted Sales Order, Sales Invoice, and Payment Entry.
- ERPNext readback verified quotation total 585, sales order total 575, paid Sales Invoice total 150, and balanced GL rows for invoice and payment.
- Sales Order amend passed with the original cancelled and the amended order submitted.
- Negative cases correctly rejected duplicate Item, missing Customer, delete submitted Sales Order, and fake Sales Order lookup.
Scope
Selling remains focused on customer and sales documents. Quote/order creation should be protected by validation or approval logic, and public reads should use Get Many with explicit fields to reduce exposure of customer and financial data.
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.