n8n-nodes-acumatica-forms
v1.5.1
Published
n8n community nodes for Acumatica ERP API with form-based inputs (enhanced fork)
Maintainers
Readme
n8n-nodes-acumatica-forms
n8n community nodes for Acumatica ERP API integration with dynamic form-based inputs.
Features dynamic form fields generated from the Acumatica OpenAPI schema — no JSON payloads required.
Installation
Install via n8n Community Nodes:
- Go to Settings → Community Nodes
- Click "Install"
- Enter
n8n-nodes-acumatica-forms
Credentials
Uses OAuth 2.0 Authorization Code flow. You'll need:
- Acumatica instance URL
- Client ID (with tenant suffix, e.g.,
GUID@TenantName) - Client Secret
Configure in Acumatica: System → Integration → Connected Applications
Nodes
- Acumatica Default 24.200.001 - For Acumatica 2024 R2
- Acumatica Default 25.200.001 - For Acumatica 2025 R2
Usage
Basic Operations
- Add an Acumatica node to your workflow
- Select the Resource (e.g.,
SalesOrder,Customer,Invoice) - Select the Operation (e.g.,
upsert,get,getList,delete) - Fill in the form fields that appear — no JSON required
Example: Create/Update a Sales Order
- Resource:
SalesOrder - Operation:
upsert - Customer ID:
CUST001 - Order Nbr:
SO001234 - Description:
My order
Expand the Details fixedCollection to add line items with Inventory ID, Quantity, etc.
Example: Query Sales Orders
- Resource:
SalesOrder - Operation:
getList - Use the Customer ID Filter → operator:
equals, value:CUST001 - Or use Custom Filter for advanced OData:
OrderDate/value gt 2024-01-01T00:00:00
Example: Get a Single Record
- Resource:
Customer - Operation:
get - ID:
CUST001
Example: Delete a Record
- Resource:
SalesOrder - Operation:
delete - ID:
SO001234
Building from Source
# Clone the repo
git clone https://gitlab.com/donny.gies/n8n-nodes-acumatica-forms.git
cd n8n-nodes-acumatica-forms
# Install dependencies
npm install
# Build (generates field definitions from swagger.json, then compiles TypeScript)
npm run build
# Link to local n8n for testing
npm link
cd ~/.n8n/nodes
npm link n8n-nodes-acumatica-forms
# Restart n8n
n8n startKnown Limitations
- Build-time only: Field definitions are generated at build time from swagger.json. If Acumatica adds new fields in a patch, rebuild the package to pick them up.
- Large resource scrolling: SalesOrder, Invoice, and other large resources have 50+ fields. Use the "Additional Fields" collection to find optional fields.
- Custom endpoints: Acumatica custom endpoints not in swagger.json are not supported via form fields. Use a generic HTTP node for those.
- No client-side field dependencies: Fields cannot conditionally appear based on other field values (n8n limitation for community nodes).
- Value wrappers always applied: All field values are wrapped in
{ value: x }format. Do not wrap values manually.
Testing
A test workflow is available at .n8n/workflows/test-v2.json covering:
upsert— PUT request with form fieldsgetList— GET with generated OData filtergetList— GET with custom OData filter stringget— GET single record by IDdelete— DELETE by ID
To use it: import the file into your n8n instance via Workflows → Import from file.
License
MIT
