JTL-FFN (Merchant v1)

Direkter REST-Zugriff auf JTL-FFN Merchant v1
Join our community

Actions5

Overview

This node provides direct REST API access to the JTL-FFN Merchant v1 service, enabling flexible interaction with the merchant backend. It supports two main modes:

  • Raw Request Mode: Allows users to perform arbitrary REST calls by specifying HTTP method, endpoint path, query parameters, body, and headers. This mode is useful for advanced users who want full control over the API requests.
  • Products Mode: Offers predefined operations related to product management such as listing products, retrieving a single product by ID, creating, updating, or deleting products. This simplifies common product-related tasks without needing to manually construct API requests.

Typical use cases include automating product catalog synchronization, managing inventory, or integrating JTL-FFN merchant data into workflows. For example, you could automatically fetch product details to enrich order processing or update product information based on external triggers.

Properties

Name Meaning
Modus Selects the mode of operation:
- Raw Request: Arbitrary REST call.
- Products: Predefined product operations (list, get, create, update, delete).
Pfad-Stil URL schema style:
- role-v1: e.g., /api/merchant-v1/...
- v1/role: e.g., /api/v1/merchant/...
Methode HTTP method for raw requests:
GET, POST, PUT, PATCH, DELETE (only shown in Raw Request mode).
Endpoint Relative API path for raw requests (without leading slash), e.g., products (only shown in Raw Request mode).
Operation Product operation to perform:
- List Products
- Get Product
- Create Product
- Update Product
- Delete Product (only shown in Products mode).
Product ID Identifier of the product for get, update, or delete operations (required in Products mode for these operations).
Update-Methode HTTP method used for updating a product:
PUT or PATCH (only shown when updating a product in Products mode).
JSON Parameter Whether to define query, body, and headers as JSON objects (true) or as UI key-value pairs (false).
Query (JSON) JSON object defining query parameters (shown if JSON Parameter is true).
Body (JSON) JSON object defining the request body (used in create/update product or raw requests with JSON Parameter true).
Headers (JSON) JSON object defining additional HTTP headers (shown if JSON Parameter is true).
Query-Parameter Key-value pairs for query parameters (shown if JSON Parameter is false).
Body-Felder Key-value pairs for body fields (shown if JSON Parameter is false and operation is create or update product).
Zusätzliche Header Key-value pairs for additional HTTP headers (shown if JSON Parameter is false).

Output

The node outputs an array of JSON objects representing the response from the JTL-FFN Merchant API. The structure depends on the called endpoint and operation:

  • For product operations, the output typically contains product data such as IDs, names, descriptions, prices, stock levels, etc.
  • For raw requests, the output reflects whatever JSON data the API returns.

No binary data output is produced by this node.

Dependencies

  • Requires an API authentication token credential for the JTL-FFN Merchant API.
  • Uses an internal helper function to perform authenticated HTTP requests to the JTL-FFN Merchant v1 endpoints.
  • No additional external dependencies beyond standard n8n environment and the configured API credentials.

Troubleshooting

  • Error: Unknown Operation — Occurs if an unsupported product operation is selected. Verify that the operation name matches one of the supported options.
  • Missing Product ID — For get, update, or delete product operations, ensure the Product ID field is filled.
  • Invalid JSON Input — When using JSON parameter mode, malformed JSON in query, body, or headers will cause errors. Validate JSON syntax before execution.
  • Authentication Errors — Ensure the API token credential is correctly configured and has sufficient permissions.
  • Endpoint Not Found — In raw mode, incorrect endpoint paths may lead to 404 errors. Double-check the relative endpoint string.
  • HTTP Method Mismatch — Using an inappropriate HTTP method for the chosen operation can cause failures; follow the documented methods per operation.

Links and References

Discussion