ERPNEXT n8n INTEGRATION: AUTOMATE ERPNEXT WITH N8N

The "Create a document" action is your gateway to automatically populating ERPNext with new records. Whether you're generating sales orders from e-commerce transactions, creating customer profiles from lead forms, or adding new inventory items from supplier catalogs, this action handles it all programmatically.

Key parameters to configure:

• Credential to connect with: Select your ERPNext account credentials from the dropdown menu. This is required to authenticate your request.
• Resource: Set to "Document" to work with ERPNext document records.
• Operation: Set to "Create" to generate a new document entry.
• DocType Name or ID: Enter the exact DocType identifier (e.g., "Sales Order", "Customer", "Item"). This text field tells ERPNext what type of document to create.
• Properties: Add key-value pairs defining the fields and values for your new document. Click "Add Property" to specify attributes like customer name, item code, quantity, etc.

Use cases where this action shines:

• Create new customer records automatically when leads convert in your CRM
• Generate purchase orders when inventory levels hit reorder points
• Add expense entries from receipt scanning applications
• Create project tasks from project management tool webhooks

The "Get a document" action retrieves a specific document from ERPNext based on its type and name. This is perfect when you need to fetch details about a particular record—like pulling customer information to personalize an email, or checking order status before triggering a follow-up action.

Key parameters to configure:

• Credential to connect with: Your ERPNext account credentials from the dropdown (required).
• Resource: Set to "Document" to target document records.
• Operation: Set to "Get" to retrieve a single document.
• DocType Name or ID: Specify the document type you want to retrieve (e.g., "Customer", "Sales Invoice").
• Document Name: Enter the unique identifier of the specific document instance (e.g., "CUST-00001" or "SINV-00023").

Use cases where this action shines:

• Fetch customer details before sending personalized communications
• Retrieve order information to include in shipping notifications
• Pull product specifications when generating quotes
• Check document status before proceeding with conditional workflow logic

The "Get many documents" action retrieves multiple records from ERPNext in a single operation. This is invaluable for batch processing, generating reports, or syncing data between ERPNext and other platforms.

Key parameters to configure:

• Credential to connect with: Your ERPNext account credentials (required).
• Resource: Set to "Document" for document record operations.
• Operation: Set to "Get Many" to retrieve multiple records.
• DocType Name or ID: Specify which document type to query (e.g., "Sales Order", "Stock Entry").
• Return All: Toggle this ON to retrieve every matching document, or OFF to limit results.
• Limit: When "Return All" is OFF, specify the maximum number of documents to return (default: 10).
• Options: Add custom fields or filters to refine your query results.

Use cases where this action shines:

• Export all pending invoices for a weekly review report
• Sync customer lists with your email marketing platform
• Retrieve all open support tickets for a dashboard
• Pull inventory items below minimum stock for reorder alerts

💡 TIP: When working with large datasets, use the "Limit" parameter strategically or add filters in the "Options" section. Retrieving thousands of documents at once can slow down your workflow and consume unnecessary resources. You can also store retrieved data in Airtable or Google Sheets for further analysis.

The "Update a document" action modifies existing records in ERPNext. From updating order statuses to adjusting inventory quantities or enriching customer profiles with new data, this action keeps your ERP data current across all your systems.

Key parameters to configure:

• Credential to connect with: Your ERPNext account credentials (required).
• Resource: Set to "Document" for document operations.
• Operation: Set to "Update" to modify an existing record.
• DocType Name or ID: Specify the document type you're targeting (e.g., "Lead", "Purchase Order").
• Document Name: Enter the unique identifier of the document to update (required).
• Properties: Add key-value pairs defining which fields to update and their new values. Click "Add Property" for each field modification.

Use cases where this action shines:

• Update lead status when they respond to marketing campaigns
• Modify inventory quantities after warehouse operations
• Change order status based on shipping carrier webhooks
• Enrich customer records with data from third-party enrichment services

The "Delete a document" action removes records from ERPNext permanently. Use this for automated cleanup tasks, removing test data, or handling deletion requests from connected systems.

Key parameters to configure:

• Credential to connect with: Your ERPNext account credentials (required).
• Resource: Set to "Document" for document operations.
• Operation: Set to "Delete" to remove the specified record.
• DocType Name or ID: Specify the document type of the record to delete (e.g., "Lead", "Quotation").
• Document Name: Enter the exact identifier of the document to remove (required).

Use cases where this action shines:

• Remove duplicate records identified by data quality workflows
• Delete test entries after development or QA processes
• Handle GDPR deletion requests by removing customer data
• Clean up expired or cancelled quotations automatically

⚠️ Important: Deletions in ERPNext are often permanent. Consider implementing an archival workflow (moving to a "Deleted" status or separate DocType) instead of outright deletion for records you might need to reference later.