Description

@taurussoftware/n8n-nodes-collmex

This is an n8n community node. It lets you read data from Collmex in your n8n workflows.

Collmex is a German cloud ERP suite covering accounting, invoicing, order processing and inventory. It exposes a CSV-over-HTTP API for exchanging data with external systems.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Compatibility
Usage
Resources
Version history

Installation

In n8n go to Settings → Community nodes → Install and enter the package name:

@taurussoftware/n8n-nodes-collmex

See the installation guide in the n8n community nodes documentation for details.

Operations

This node is read-only. It queries Collmex but never creates or changes anything.

| Resource | Operations | Collmex query | Returns |
| — | — | — | — |
| Customer | Get, Get Many | CUSTOMER_GET | CMXKND |
| Vendor | Get, Get Many | VENDOR_GET | CMXLIF |
| Product | Get, Get Many | PRODUCT_GET | CMXPRD |
| Quotation | Get, Get Many | QUOTATION_GET | CMXQTN |
| Sales Order | Get, Get Many | SALESORDERGET | CMXORD-2 |
| Invoice | Get, Get Many | INVOICE_GET | CMXINV |
| Delivery | Get, Get Many | DELIVERY_GET | CMXDLV |

Each resource has an Options collection for the filters the corresponding Collmex query supports, such as date ranges, customer number, free text search and a company override.

Credentials

You need a Collmex account with API access, plus a dedicated API user.

1. Create an API user. In Collmex go to Administration → Users → New and enable the API-only flag, labelled “Nur fuer API” in the German interface. This is mandatory: your normal interactive login is rejected by the API with MESSAGE;E;101026. Collmex does not charge for extra users carrying this flag.
2. Look up your customer number. This is your Collmex tenant number, the one that appears in the API endpoint URL.
3. In n8n create Collmex API credentials and fill in:
– Customer Number – your tenant number
– User / Password – the API user from step 1
– Company ID – the internal company number, 1 unless you run several companies

Press Test to verify. The test reports the actual Collmex message when something is wrong, because Collmex answers a failed login with HTTP 200 rather than an error status.

Compatibility

Tested against n8n 1.x with n8n-workflow as a peer dependency. No known incompatibilities.

Usage

Field names instead of CSV columns

The Collmex API speaks CSV, where every field is identified only by its position. This node maps those positions onto named, typed fields, so a customer arrives as { customerId: 10000, zip: "01069", city: "Dresden", createdAt: "2026-09-11" } rather than as a numbered array.

A few details worth knowing:

• Dates are normalised to ISO (2026-09-11), whichever of the two Collmex formats the server used.
• Amounts and quantities are converted from the German decimal comma, so 1.234,50 becomes 1234.5.
• Coded values usually arrive from Collmex with a label glued behind the number (20 Offen). The node splits these, giving you both status: 20 and statusLabel: "Offen".
• Empty fields are omitted rather than returned as null, so an item only carries what Collmex actually filled in.
• Undocumented fields are preserved. Collmex occasionally returns more columns than it documents (CMXLIF has 42 against 41 in the specification). Surplus columns appear as field42, field43 and so on rather than being dropped.

Documents and their line items

Quotations, sales orders, invoices and deliveries are returned by Collmex as one row per line item, with the header data repeated on every row. The Group Positions option (on by default) folds those rows back into one item per document, with the line items in a positions array. Turn it off to get one item per row.

Limit

Collmex has no server-side paging: every query returns the complete result set. The Limit option therefore only trims the output after the response has already been transferred. Use the filters in Options if you want Collmex itself to return less.

Incremental sync

Most queries support Only Changed together with System Name. Collmex stores the timestamp of the last query per system name, so a scheduled workflow using a stable system name (for example n8n) will only receive records created or changed since its previous run.

Resources

• n8n community nodes documentation
• Collmex API documentation (German)
• Collmex API overview (German)

Version history

0.2.0

Adds the Product resource, and every record type is now verified against data
Collmex actually returned rather than against the documentation alone.

Two breaking changes, both small:

• Items no longer carry a recordType property. It named the CSV record type

rather than describing the record, and you already know which resource you
queried. A workflow reading $json.recordType has to drop that reference.

• The Request Character Set credential field is gone; requests always use

UTF-8. Nothing needs re-entering, the stored value is simply ignored.

0.1.6

No functional change over 0.1.5; released so the package could be resubmitted for verification. Verified for n8n Cloud from this version on.

0.1.5

The credential test detects invalid credentials again, reverting the 0.1.4 change. No change to resources, operations or output.

0.1.4

The credential test no longer detects invalid credentials. No change to resources, operations or output.

0.1.3

Makes the credential test self-contained so n8n’s automated review can determine it. No change to resources, operations or output.

0.1.2

Fixes the credential test so n8n’s automated review recognises it. No change to resources, operations or output.

0.1.1

Internal rework of authentication and the credential test so the package passes n8n’s community package scanner. No change to resources, operations or output.

0.1.0

First release. Read-only access to customers, vendors, quotations, sales orders, invoices and deliveries.