TaxMetall ERP

v1.26.2

Last updated Aug 20, 2026

n8n community node for TaxMetall ERP — read customers, articles, orders, offers, invoices, delivery notes, purchase inquiries, purchase orders, purchase invoices, suppliers, dunning, and execute statistics queries via the TaxMetall REST API.

340 Weekly Downloads

696 Monthly Downloads

View on NPM GitHub Repository

Included Nodes

TaxMetall ERP

Description

n8n-nodes-taxmetall

![npm version](https://www.npmjs.com/package/@vectotaxsoftwaregmbh/n8n-nodes-taxmetall)
![License: MIT](https://opensource.org/licenses/MIT)

An n8n community node package that connects TaxMetall ERP and TaxDMS to your workflows. Read and create records across all major ERP domains — customers, articles, orders, offers, invoices, delivery notes, purchase inquiries, purchase orders, purchase invoices, suppliers, dunning — and run custom SQL reports and upload documents to TaxDMS, all directly from n8n.

TaxMetall is an ERP system for metal trading and processing companies, developed by Vectotax Software GmbH.

—

Installation
Credentials
Node: TaxMetall ERP

– Acquisition
– Article
– Customer
– Customer Inquiry
– Delivery Note
– DMS
– Document Sync (SharePoint WF1 / WF2)
– Dunning
– Invoice
– Offer
– Order
– Purchase Inquiry
– Purchase Invoice
– Purchase Order
– Statistic
– Supplier

Compatibility

– Required TaxMetall API Service version
– Finding your service version

Resources
License

—

Installation

Follow the n8n community nodes installation guide.

Via the n8n UI:
1. Go to Settings → Community Nodes
2. Click Install a community node
3. Enter @vectotaxsoftwaregmbh/n8n-nodes-taxmetall
4. Click Install

Via CLI:

npm install @vectotaxsoftwaregmbh/n8n-nodes-taxmetall

—

Credentials

Create a TaxMetall API credential in n8n (Settings → Credentials → New → TaxMetall API).

The API key is automatically injected as the tax-api-key HTTP header with every request.

Use the Test button to verify the connection. From service version 1.26.0 on, the response also
carries the version of the service you are connected to — worth checking against
Required TaxMetall API Service version before you build a
workflow around a newer resource.

—

Node: TaxMetall ERP

The TaxMetall ERP node covers all major TaxMetall domains. Select a Resource and then an Operation to configure the node.

—

Acquisition

Manages acquisition/lead contacts in TaxMetall.

#### Create

Creates a new acquisition entry.

#### Search by ID

Returns a single acquisition entry by its internal contact number.

| Field | Required | Description |
|—|—|—|
| Acquisition ID | Yes | Internal contact number (KontaktNr) |

#### Search by Name

Searches acquisition entries by partial match on company or contact name.

| Field | Required | Description |
|—|—|—|
| Name | Yes | Partial name to search for |

#### Search by Date Range

Lists acquisition entries by their first contact date.

| Field | Required | Description |
|—|—|—|
| Date From | Yes | Start date in format yyyy-mm-dd |
| Date To | Yes | End date in format yyyy-mm-dd |

—

Article

Manages articles (Artikel) in TaxMetall.

#### Create

Creates a new article. If no article number is provided, the next number from the configured number range is used automatically.

#### Search by Article ID

Returns an article by its internal numeric ID.

| Field | Required | Description |
|—|—|—|
| Article ID | Yes | Internal article ID (AID) |

#### Search by Article Number

Returns an article by its exact article number.

| Field | Required | Description |
|—|—|—|
| Article Number | Yes | Article number (Artikelnr) |

#### Search by Drawing Number

Searches articles by drawing or part number.

| Field | Required | Description |
|—|—|—|
| Drawing Number | Yes | Drawing number (Zeichnungsnr) |

#### Search by Name

Searches articles by partial match on the article name.

| Field | Required | Description |
|—|—|—|
| Name | Yes | Partial name to search for |

—

Customer

Manages customers (Kunden) in TaxMetall.

#### Create

Creates a new customer.

#### Search by ID

Returns a customer by their customer number.

| Field | Required | Description |
|—|—|—|
| Customer ID | Yes | Customer number (Kundennr) |

#### Search by Name

Searches customers by partial match on their company name.

| Field | Required | Description |
|—|—|—|
| Customer Name | Yes | Partial name to search for |

#### Search by Order ID

Returns the customer associated with a given order number.

| Field | Required | Description |
|—|—|—|
| Order ID | Yes | Order number (Auftragnr) |

—

Customer Inquiry

Creates and reads customer inquiries (Kundenanfragen) in TaxMetall — the request-for-quote a customer
sends you, before it becomes an offer. Backed by the ERP tables KundenAnfrage, KundenAnfragePos
and KundenAnfrageHistorie.

> Requires TaxMetall API Service 1.25.0 or newer for all operations of this resource. See
> Compatibility.

#### Create

Creates a new customer inquiry with one or more positions. A position may reference an article
(Article ID or Article Number) or be a pure free-text position — for a new part coming in as
a drawing, a Description alone is enough. When an article is given, description, unit, drawing
number, revision and the preferred supplier are taken from the article master.

Customer Source decides which master the customer number refers to: Existing Customer
(Kundens) or Prospect (Neukundens, the acquisition table also used by the Acquisition
resource). Address and contact data are copied into the inquiry header from whichever master applies.

Some fields are validated against ERP selection lists (Listen) and are rejected with the list of
allowed entries if they do not match: Subject (KAnfrageBetreff), Order Type (Auftragsart),
Estimated Value (Schaetzwert) and, in the history entry, Text, Type, Contact Type and
Status. Inquiry Channel and Document Status are free text.

> Note on Subject: in the ERP the subject line lives in the database column Status — the field is
> named Subject here to match what the ERP mask shows. The workflow status is Document Status
> (BelegStatus).

If positions carry a Value, their sum is written to the inquiry header, mirroring the ERP.

#### Search by Inquiry No.

Returns a single inquiry including its positionen[] and historie[].

| Field | Required | Description |
|—|—|—|
| Inquiry Number | Yes | anfragenr |

#### Search by Customer No. / Search by Email / Search by Date Range

Return a list of inquiry headers. Search by Email matches the email address stored on the inquiry,
which makes it useful for assigning an incoming mail to an existing inquiry.

| Field | Required | Description |
|—|—|—|
| Customer Number / Email / Date From + Date To | Yes | Depending on the operation |
| Additional Filters | No | Document status, order type, priority, inquiry channel, project, offer number, customer reference, customer source, limit |

—

Delivery Note

Reads delivery notes (Lieferscheine) including their line items.

#### Search by Delivery Note No.

Returns a single delivery note with all its line items.

| Field | Required | Description |
|—|—|—|
| Delivery Note Number | Yes | Delivery note number (Lieferscheinnr) |

#### Search by Customer No.

Lists all delivery notes for a given customer.

| Field | Required | Description |
|—|—|—|
| Customer Number | Yes | Customer number (Kundennr) |

#### Search by Date Range

Lists all delivery notes within a date range.

| Field | Required | Description |
|—|—|—|
| Date From | Yes | Start date in format yyyy-mm-dd |
| Date To | Yes | End date in format yyyy-mm-dd |

—

DMS

Uploads files to the TaxDMS document management system (Vectotax Software GmbH).

#### Create File

Uploads a binary file together with a metadata object to TaxDMS via the /api/create-dms-file endpoint. The file is transferred as Base64.

| Field | Required | Description |
|—|—|—|
| Data (JSON) | Yes | Metadata object — structure defined by your TaxDMS configuration |
| File (Binary) | Yes | Name of the n8n binary property that holds the file, e.g. data |

> Tip: Use an HTTP Request node, a Read Binary File node, or any node that outputs a binary property to provide the file. The value of File (Binary) must match the property name under which n8n stores the file in that node’s output.

—

Document Sync (SharePoint WF1 / WF2)

Connects the TaxMetall document pocket (Dokutasche) with SharePoint through the TaxMetall document-sync work queue (APIEventTrigger / APIEventDetail). It implements two workflows:

WF1 — Export (TaxMetall → SharePoint): claim newly created documents from the queue, download each file, upload it to SharePoint, then report the result back so the entry is closed or retried.
WF2 — Import (SharePoint / mail → TaxMetall): create a document (typically an .eml built by the service) in TaxMetall and write a closing audit entry, with optional deduplication by mail message ID.

The service stores the resulting SharePoint URL under Payload.sharePoint.mainUrl and, for WF2, the mail ID under Payload.email.messageId.

> Requires TaxMetall API Service 1.20.3 or newer; the Unpack MSG File operation requires
> 1.23.2 or newer. See Compatibility.

#### Check New Documents

Claims up to Limit pending entries from the work queue and returns the list of documents to process (WF1, step 1). Claim locking is handled in-memory per tenant by the service — there is no token to pass around.

| Field | Required | Description |
|—|—|—|
| Limit | No | Max number of documents to claim in one call (default 50). The service caps this at its configured maximum. |

Important response fields:

| Field | Description |
|—|—|
| busy | true when another batch is still being processed; then documents[] is empty and nothing is claimed — simply poll again later |
| documents[] | Entries ready for processing |
| documents[].syncId | Queue entry ID — needed for download and status report |
| documents[].downloadUrl | Ready-to-use relative URL /api/document-file?syncId=… (CREATE only) |
| documents[].eventTyp | Event type as integer: 1 = CREATE, 3 = DELETE |
| documents[].aktion | The same event as text: CREATE or DELETE |
| documents[].belegTyp / belegNr | Business document type (e.g. Auftrag, Rechnung, Angebot) and document number — the internal table name is not exposed |
| documents[].dateiname | Source file path/name |
| documents[].email | For mail documents (Typ=2) on CREATE events: { from, to, subject, date } from the document record — handy when uploading the mail to storage. Absent for non-mail documents. |
| documents[].payload | For DELETE events only: the full payload object that was stored on the prior upload (the transfer-status payload, or — for documents imported via Create Document — { "sharePoint": { "mainUrl": … } }), so you can remove the file from SharePoint. Read the URL from payload.sharePointUrl or payload.sharePoint.mainUrl. null if no prior upload is found / already purged by retention. |
| skipped[] | Entries the service skipped this batch (informational only — nothing to download/upload) — dmsreference (a DMS: pointer, not a local file) or filenot_found (the referenced file is no longer on disk). Both occur only on CREATE events and the queue row is removed permanently. |

Coalescing (per file path): Between two polls the same file can be created/deleted several times (e.g. created → deleted → created). For SharePoint only the final state matters. Coalescing is handled in the ERP trigger itself (only the latest event per file path / highest syncId is kept in the queue), so superseded earlier events never reach check-new-documents — there is no superseded skip reason. Combined with the delete correlation this means: a created→deleted pair where nothing was ever uploaded collapses to a no-op (the kept DELETE event returns payload: null), while created→deleted→created collapses to a single upload of the latest version.

#### Download Document File

Downloads the file of a single claimed entry as binary data (WF1, step 2). The node parses the file name from the response and sets the MIME type automatically.

| Field | Required | Description |
|—|—|—|
| Sync ID | Yes | syncId of the entry (from Check New Documents) |
| Put Output File in Field | Yes | Name of the binary property to write the file to (default data) |

The downloaded file is placed in the chosen binary property, ready for an upload node (e.g. HTTP Request or a Microsoft SharePoint node). The item JSON also carries syncId, fileName and mimeType.

#### Check & Download New Documents

Combines Check New Documents and Download Document File into a single step (WF1, steps 1 + 2). It claims a batch from the queue and downloads the file for each CREATE entry (those with a downloadUrl) — so you no longer need a Split/loop + a separate download node.

| Field | Required | Description |
|—|—|—|
| Limit | No | Max number of documents to claim in one call (default 50). The service caps this at its configured maximum. |
| Put Output File in Field | Yes | Name of the binary property to write each file to (default data) |

Output: one item per claimed document — and exactly one summary item when nothing was found, so the node always returns something to branch on.

Nothing found: a single item { "success": false, "count": 0, "description": "No new documents found" } (no binary). Use this to drive a “nothing to do” branch.
Documents found: one item per claimed document. Every item carries success: true, count (number of documents in the batch) and index (0-based position), in addition to:

– CREATE entries (with a file): the full document metadata plus fileName and mimeType; the file is in the chosen binary property — ready to wire straight into an upload node.
– Non-file events (e.g. DELETE): metadata only, no binary.
– If a single file fails to download (it was removed or skipped server-side between claim and download), that item carries downloadError and httpCode instead of a binary; the rest of the batch still comes through.

Tip: filter downstream on {{ $json.success }} to separate the “found” items from the empty-result item.

Because the syncId is on every found item, a downstream Report SharePoint Transfer Status can acknowledge each entry as usual. Use the low-level Check New Documents / Download Document File operations only when you need full manual control over the claim/download split.

#### Report SharePoint Transfer Status

Reports the upload result back to the service (WF1, step 4).

Retry handling: on success = false the service keeps the work-queue row, so the document is retried on the next poll — unconditionally and without limit (there is no retry counter and no dead state). The failure is recorded only in the service log.

#### Create Document

WF2: creates a document in TaxMetall from mail data. When no existing file path is supplied, the service builds a standards-compliant .eml (via Indy) from the email fields and attachments, links it to the target record, and writes a closing audit entry (Quelle = API:create-new-dokument). A CONTEXT_INFO marker prevents the ERP trigger from re-syncing the document (no loop).

| Field | Required | Description |
|—|—|—|
| Area (Bereich) | Yes | Target area, chosen from a dropdown. Position documents are attached to the article, so use Article (Artikel) for those. |
| Document Number (Belegnummer) | Yes | Number of the target record. For position documents use the article number. |
| SharePoint URL | No | Optional source SharePoint URL (stored under Payload.sharePoint.mainUrl when set). Leave empty to create the document without a SharePoint reference — e.g. when the export to storage is handled later by WF1 (enable Also Export to Storage). |
| Email To | No* | Recipient address (email.an) — required when the service generates the .eml |
| Attach All Input Binary Fields | No | Attach every binary property on the input item automatically (variable number of files, e.g. all attachments from a Gmail/IMAP trigger). When on, the manual Attachments list is hidden and ignored. |
| Allow Duplicates | No | Skip deduplication. Off by default. |
| Also Export to Storage (Disable Loop Guard) | No | Off by default — the imported document is not re-exported. Enable to additionally queue the created document for export (WF1), e.g. to mirror it to SharePoint. |

Area (Bereich) mapping — the dropdown sends these table names. Documents attached from positions use Artikel_s with BelegNr = ArtikelNr.

Email Fields (collection — used to build the .eml):

*When the service builds the .eml, email.an and at least one of email.text / email.html are required; otherwise the API returns 400.

Attachments (add one row per file):

> Binary handling: the most convenient way to add attachments is to wire a node that outputs binary data (e.g. HTTP Request, Read Binary File, a SharePoint download) and reference its binary property under Input Binary Field — the node performs the Base64 conversion for you. The combined upload is bounded by the service limit (MAXUPLOADSIZE, 60 MB request body ≈ 45 MiB of decoded attachments); a larger request is rejected with 403 Forbidden.

Deduplication & allowDuplicates:

The duplicate check matches on the previously stored JSON_VALUE(Payload, '$.email.messageId') of WF2 audit entries.

#### Example workflows

WF1 — Export to SharePoint (combined, recommended):

[Schedule/Trigger]
      ↓
[TaxMetall ERP · Document Sync · Check & Download New Documents] → one item per document, binary "data"
      ↓
[Upload to SharePoint]                                          → sharePointUrl
      ↓
[TaxMetall ERP · Document Sync · Report Transfer Status]        (success = true, Payload Field sharePointUrl)

WF1 — Export to SharePoint (manual claim/download split):

[Schedule/Trigger]
      ↓
[TaxMetall ERP · Document Sync · Check New Documents]   → documents[]
      ↓ (Split / loop over documents[])
[TaxMetall ERP · Document Sync · Download Document File] → binary "data"
      ↓
[Upload to SharePoint]                                  → sharePointUrl
      ↓
[TaxMetall ERP · Document Sync · Report Transfer Status] (success = true, Payload Field sharePointUrl)

On an upload failure, set Success = false and pass the error message — the entry stays in the queue and is retried on the next poll, unconditionally and without limit (no retry counter, no dead state).

WF2 — Import from SharePoint / mail:

[SharePoint / Mail source]
      ↓
[TaxMetall ERP · Document Sync · Create Document]  (bereich, belegnummer, sharePointUrl, email, attachments)

#### Example JSON for Create Document

The node assembles the request below from its fields. The same body can also be sent directly to POST /api/create-new-dokument:

{
  "bereich": "Auftrag_s",
  "belegnummer": "10523",
  "sharePointUrl": "https://contoso.sharepoint.com/sites/erp/Freigegebene%20Dokumente/10523.eml",
  "allowDuplicates": false,
  "email": {
    "messageId": "",
    "von": "kunde@example.com",
    "an": "vertrieb@firma.de",
    "betreff": "Bestellung 10523",
    "datum": "2026-06-15T09:30:00",
    "text": "Anbei die Bestellung.",
    "html": "Anbei die Bestellung."
  },
  "attachments": [
    {
      "dateiname": "bestellung.pdf",
      "mimeType": "application/pdf",
      "inhaltBase64": "JVBERi0xLjcZ…"
    }
  ]
}

Successful response (new document):

{ "success": true, "emlGenerated": true, "messageId": "" }

Duplicate response (same messageId, allowDuplicates off):

{ "success": true, "duplicate": true, "message": "Mail bereits verarbeitet" }

#### Typical errors

| Status | Meaning |
|—|—|
| 400 Bad Request | Missing/invalid field — e.g. bereich/belegnummer missing, no sharePointUrl, email.an or body missing, invalid Base64, or allowDuplicates not boolean |
| 401 Unauthorized | API key (tax-api-key header) missing or invalid |
| 403 Forbidden | Request body exceeds MAXUPLOADSIZE, or the source file is not readable |
| 404 Not Found | Queue entry or source file not found; or an invalid target reference for WF2 |
| 409 Conflict | Wrong event type (e.g. a DELETE event has no file to download), or a DMS: reference that cannot be delivered as a local file |
| 503 Service Unavailable | Document sync disabled in the service config, or the APIEvent tables (APIEventTrigger/APIEventDetail) not present for the tenant — run syncschema-init |

—

Dunning

Reads open dunning items (Mahnungen). Dunning records are not independent documents in TaxMetall — they are a filtered view of the invoice table (open balance > 0, not a credit note, no dunning block active).

#### Search by Customer No.

Lists all open dunning items for a specific customer.

#### Search by Due Date Range

Lists all open dunning items within a due date range.

—

Invoice

Reads invoices (Rechnungen) including their line items.

#### Search by Invoice No.

Returns a single invoice with all its line items.

| Field | Required | Description |
|—|—|—|
| Invoice Number | Yes | Invoice number (Rechnungnr) |

#### Search by Customer No.

Lists all invoices for a given customer.

| Field | Required | Description |
|—|—|—|
| Customer Number | Yes | Customer number (Kundennr) |

#### Search by Date Range

Lists all invoices within a date range (by invoice date).

| Field | Required | Description |
|—|—|—|
| Date From | Yes | Start date in format yyyy-mm-dd |
| Date To | Yes | End date in format yyyy-mm-dd |

—

Offer

Manages offers (Angebote) in TaxMetall.

#### Create

Creates a new offer for a customer with one article position. Either Article ID or Article Number must be provided — if both are set, Article ID takes precedence.

*At least one of Article ID or Article Number must be provided.

#### Search by Offer No.

Returns a single offer with all its line items.

| Field | Required | Description |
|—|—|—|
| Offer Number | Yes | Offer number (Angebotsnr) |

#### Search by Customer No.

Lists all offers for a given customer.

| Field | Required | Description |
|—|—|—|
| Customer Number | Yes | Customer number (Kundennr) |

#### Search by Date Range

Lists all offers within a date range (by offer date).

| Field | Required | Description |
|—|—|—|
| Date From | Yes | Start date in format yyyy-mm-dd |
| Date To | Yes | End date in format yyyy-mm-dd |

—

Order

Creates and reads orders (Aufträge) in TaxMetall.

#### Create

Creates a new order for a customer with one or more article positions. For each position, either Article ID or Article Number must be provided — if both are set, Article ID takes precedence. Header and position data (addresses, VAT, prices, discounts, open quantity) are derived automatically from the customer and article master data, and the order totals are calculated.

*At least one of Article ID or Article Number must be provided per position.

Each created position is marked in the Text1 field with the note “Erstellt durch TaxMetall API Service”.

#### Get Order Status

Returns a single order including all its line items and current production status.

| Field | Required | Description |
|—|—|—|
| Order Number | Yes | Internal order number (Auftragnr) |

#### Search by Date Range

Lists all orders within a date range.

| Field | Required | Description |
|—|—|—|
| Date From | Yes | Start date in format yyyy-mm-dd |
| Date To | Yes | End date in format yyyy-mm-dd |

—

Purchase Inquiry

Creates and reads purchase inquiries (Anfragen) to suppliers in TaxMetall.

> Requires TaxMetall API Service 1.24.0 or newer for all operations of this resource. See
> Compatibility.

#### Create

Creates a new purchase inquiry for a supplier with one or more article positions. For each position, either Article ID or Article Number must be provided — if both are set, Article ID takes precedence.

*At least one of Article ID or Article Number must be provided per position.

#### Search by Inquiry No.

Returns a single purchase inquiry including all its line items.

| Field | Required | Description |
|—|—|—|
| Inquiry Number | Yes | Purchase inquiry number (AnfrageNr) |

#### Search by Supplier

Lists all purchase inquiries for a given supplier.

| Field | Required | Description |
|—|—|—|
| Supplier Number | Yes | Supplier number (Liefernr) |

#### Search by Date Range

Lists all purchase inquiries within a date range (by inquiry date).

| Field | Required | Description |
|—|—|—|
| Date From | Yes | Start date in format yyyy-mm-dd |
| Date To | Yes | End date in format yyyy-mm-dd |

—

Purchase Invoice

Reads incoming purchase invoices (Eingangsrechnungen) including their line items, and creates them
either from individual fields or from an EN 16931 e-invoice file.

> The Search operations work with TaxMetall API Service 1.10.0 or newer. The Create
> operation requires 1.25.0 or newer. See Compatibility.

#### Search by Purchase Invoice No.

Returns a purchase invoice by its invoice number. If multiple entries share the same invoice number (from different suppliers), add the supplier number to narrow the result.

| Field | Required | Description |
|—|—|—|
| Purchase Invoice Number | Yes | Purchase invoice number (ERNr) |
| Supplier Number | No | Supplier number to narrow results when the invoice number is not unique |

#### Search by Supplier

Lists all purchase invoices for a given supplier.

| Field | Required | Description |
|—|—|—|
| Supplier Number | Yes | Supplier number (Liefernr) |

#### Search by Date Range

Lists all purchase invoices within a date range (by invoice date).

| Field | Required | Description |
|—|—|—|
| Date From | Yes | Start date in format yyyy-mm-dd |
| Date To | Yes | End date in format yyyy-mm-dd |

—

Purchase Order

Creates and reads purchase orders (Bestellungen) to suppliers in TaxMetall.

> Requires TaxMetall API Service 1.24.0 or newer for all operations of this resource. See
> Compatibility.

#### Create

Creates a new purchase order for a supplier with one or more article positions. For each position, either Article ID or Article Number must be provided — if both are set, Article ID takes precedence.

*At least one of Article ID or Article Number must be provided per position.

#### Search by Order No.

Returns a single purchase order including all its line items.

| Field | Required | Description |
|—|—|—|
| Order Number | Yes | Purchase order number (BestellNr) |

#### Search by Supplier

Lists all purchase orders for a given supplier.

| Field | Required | Description |
|—|—|—|
| Supplier Number | Yes | Supplier number (Liefernr) |

#### Search by Date Range

Lists all purchase orders within a date range (by order date).

| Field | Required | Description |
|—|—|—|
| Date From | Yes | Start date in format yyyy-mm-dd |
| Date To | Yes | End date in format yyyy-mm-dd |

—

Statistic

Executes pre-configured SQL reports stored in TaxMetall and returns the results as a JSON array. This covers both custom SQL reports and Business Cockpit reports defined in your TaxMetall installation.

The available reports are loaded dynamically from the API and presented in a dropdown — each option shows the report name and which parameters it requires.

> Note: Only reports of type Individual (Individuell) and Business Cockpit (BC) are supported. Static system reports (Statisch) are not available because their SQL is not stored in the database.

#### Execute

Additional Parameters (collection — add only what the report requires):

—

Supplier

Manages suppliers (Lieferanten) in TaxMetall.

#### Create

Creates a new supplier.

#### Search by ID

Returns a supplier by their supplier number.

| Field | Required | Description |
|—|—|—|
| Supplier Number | Yes | Supplier number (Liefernr) |

#### Search by Name

Searches suppliers by partial match on their company name.

| Field | Required | Description |
|—|—|—|
| Name | Yes | Partial name to search for |

#### Search by Article

Returns all suppliers linked to a specific article via the supplier-article assignment table.

| Field | Required | Description |
|—|—|—|
| Article Number | Yes | Article number from the supplier-article assignment |

—

Compatibility

| Requirement | Version |
|—|—|
| n8n | >= 1.0.0 |
| Node.js | >= 18 |
| n8n Nodes API | 1 |

Required TaxMetall API Service version

Every operation of this node calls an endpoint of the TaxMetall API Service running on your
premises. Those endpoints were added over time, so an operation only works if the service on
the other end is new enough. The node does not check this for you: calling an operation
your service does not know yet returns HTTP 404 with Endpoint nicht gefunden.

Newer service versions never remove endpoints, so a service that is at or above the highest
version listed below covers everything in this package.

Finding your service version

From service version 1.26.0 on, /api/validate reports the version it is running, so the
Test button on the TaxMetall API credential shows it directly. You can also read it with:

curl -H "tax-api-key: YOUR_KEY" https://your-host:8443/api/validate

{ "success": true, "message": "Connected", "version": "1.26.0", "mandant": 1, "mandantname": "Example GmbH", "dbconnected": true }

Older services answer the same call without a version field. In that case the version is in
the first lines of the service log file, and in Windows → Programs and Features next to
TaxMetall API Service.

—

Resources

Vectotax Software GmbH
n8n community nodes documentation
npm package
Report an issue

—

License

MIT

Included Nodes

Description

n8n-nodes-taxmetall

Table of Contents

Installation

Credentials

Node: TaxMetall ERP

Acquisition

Article

Customer

Customer Inquiry

Delivery Note

DMS

Document Sync (SharePoint WF1 / WF2)

Dunning

Invoice

Offer

Order

Purchase Inquiry

Purchase Invoice

Purchase Order

Statistic

Supplier

Compatibility

Required TaxMetall API Service version

Finding your service version

Resources

License

More in CRM

ChatWoot

ChatWoot

Close

Autotask

NetSuite

LiveConnect

Chatwoot fazer.ai

Bitrix