ERPNext n8n integrationAutomate ERPNext with n8n.
Can a single node really drive an entire ERP? The ERPNext n8n integration exposes one resource, Document, and 5 operations on it, which is enough to create, read, update and delete any DocType in your instance. No trigger node ships with it, so a schedule or a webhook starts the run.
Verified Trustpilot reviews · AI, automation & growth agency
What does the ERPNext n8n integration actually give you?
The ERPNext n8n integration is one node that talks to the ERPNext API using an API key and secret. It exposes a single resource, Document, with 5 operations: create, delete, get, get many and update. Since ERPNext models nearly every object as a DocType, those 5 operations reach far more than 5 kinds of record.
Intake is the first pattern. A row added to a Google Sheets tab, a webhook fired by a website form, or a payload cleaned up by an AI step can all end with document.create writing a Customer into ERPNext. The workflow fills the Properties collection field by field, and ERPNext returns the document name it assigned.
Reporting comes next. document.getAll with Return All enabled walks every page of the API and brings back the full set of documents for a DocType, while Field Names or IDs trims the payload down to the columns that matter. Send the result to Slack as a morning digest, or write it back to a sheet for the finance team.
The third pattern keeps ERPNext in step with the tools around it. A payment recorded in Stripe or an entry posted in Quickbooks can feed document.update, which changes only the properties you list and leaves the rest of the record untouched.
Reach for HTTP Request when the node stops short. It covers one resource, Document, and nothing else. Anything else the ERPNext API exposes, such as running a report or calling a server method, sits outside the node. HTTP Request calls any endpoint and reuses the same ERPNext credential through predefined authentication, so there is no second key to manage.
Two limits are worth knowing before you build. ERPNext has no trigger node in n8n, so every workflow starts somewhere else: a Schedule Trigger on a fixed interval, an n8n Webhook called by another service, or the trigger of another app. And create, get, update and delete each handle one document per item, so bulk work means looping over items. If n8n itself is new to you, the n8n training covers that groundwork.
How do you connect ERPNext to n8n?
- 01
Generate an API key and secret
In ERPNext, open Settings, then My Settings, then API Access, and generate an API Key. The API Secret is produced alongside it and shown once, so copy both before leaving the screen. The key inherits the permissions of the user account it belongs to, which is the simplest way to scope what your workflows can touch. A System Manager can also generate keys and secrets for other users.
- 02
Tell n8n where ERPNext lives
The credential needs an Environment. For a cloud-hosted account, give your Subdomain and pick a Domain between
erpnext.comandfrappe.cloud. For a self-hosted instance, give the fully qualified Domain where ERPNext runs. There is also Ignore SSL Issues, which lets n8n connect when certificate validation is unavailable. - 03
Save it once, reuse it everywhere
A credential is created once in the Credentials menu of n8n and then offered in the dropdown of every ERPNext node you add, on n8n Cloud and on a self-hosted instance alike. The same credential also backs an HTTP Request node through predefined authentication, which is how you reach ERPNext endpoints the node does not cover without storing a second copy of your key.
What can the ERPNext node do?
The ERPNext node exposes 5 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Document
5 operationsCreate a document
document.createWhat you see in n8n
Notes & use cases
Pick a record type, describe its fields, and n8n writes a new document into ERPNext. The response carries the document name that ERPNext assigned, which you reuse downstream.
Key parameters
- DocType Name or ID: the type of record being created, chosen from the list n8n loads from your instance or set with an expression such as
{{ $json.docType }}. The placeholder showsCustomer. - Properties: one entry per field you want to fill, added through Add Property. Fields you leave out keep whatever the DocType defines for them.
Delete a document
document.deleteWhat you see in n8n
Notes & use cases
Removes one record from ERPNext for good. Nothing comes back except confirmation, so put whatever you need to keep in a node before this one.
Key parameters
- DocType Name or ID: the type of record being deleted, since a name is only unique inside its own type.
- Document Name: the name, meaning the ID, of the document to delete, usually carried over from an earlier step as
{{ $json.name }}.
Get a document
document.getWhat you see in n8n
Notes & use cases
Reads one record and hands its full field set to the next node. Useful whenever a workflow knows an ID but needs the details behind it.
Key parameters
- DocType Name or ID: the type of record to read, picked from the list or passed as an expression.
- Document Name: the name, meaning the ID, of the document you want back.
Get many documents
document.getAllWhat you see in n8n
Notes & use cases
Lists documents of a type instead of fetching one by name. Every parameter here is optional, so it is the one to reach for when exploring an instance.
Key parameters
- DocType Name or ID: which type to list, with
Customeras the placeholder. - Return All: on, n8n pages through the API until every matching document is returned; off, it stops at Limit.
- Limit: the maximum number of documents returned when Return All is off.
- Field Names or IDs: the fields to return, comma separated, such as
name,country. - Filters: custom properties added one by one to narrow the list.
Update a document
document.updateWhat you see in n8n
Notes & use cases
Changes an existing record in place. Only the properties you list are touched, so a partial update is the normal case rather than a special one.
Key parameters
- DocType Name or ID: the type of the record being updated.
- Document Name: the name, meaning the ID, of the document to modify.
- Properties: the fields to overwrite, added through Add Property. Leave it empty and nothing changes.
Need help automating ERPNext with n8n?
A person reads every message.
