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, allowing users to perform various operations on products or make arbitrary REST calls. It supports two modes:

  • Raw Request: Users can specify any HTTP method, endpoint path, query parameters, body, and headers for flexible API interaction.
  • Products: Offers predefined product-related operations such as listing, retrieving, creating, updating, and deleting products.

A common use case is managing product data in a JTL-FFN Merchant system within an automated workflow, e.g., deleting a product by its ID. The node simplifies integration with the JTL-FFN Merchant API without manual HTTP request construction.

Example scenario:

  • Automatically delete a product from the merchant catalog when it is discontinued in another system by specifying the product ID and using the "Delete Product" operation.

Properties

Name Meaning
Modus Mode of operation:
- Raw Request: Any 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 mode).
Endpoint Relative API path for raw requests (without leading slash), e.g., products (only shown in Raw 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 to get, update, or delete (required for get, update, delete operations in Products mode).
Update-Methode HTTP method for updating a product:
PUT or PATCH (only shown for update operation 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 for create and update operations, shown if JSON Parameter is 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).
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 call. For example, when deleting a product, the output will contain the API's response confirming deletion or error details.

  • The output field json contains the parsed JSON response.
  • No binary data output is indicated.

Dependencies

  • Requires an API authentication token credential for the JTL-FFN Merchant API.
  • Uses an internal helper function to send HTTP requests to the JTL-FFN Merchant API endpoints.
  • No other external dependencies are required.

Troubleshooting

  • Unknown Operation Error: If an unsupported product operation is selected, the node throws an error like Unbekannte Operation. Ensure the operation name matches one of the supported options.
  • Missing Product ID: For get, update, or delete product operations, the product ID must be provided; otherwise, the API call will fail.
  • Invalid JSON Parameters: When using JSON input for query, body, or headers, ensure valid JSON syntax to avoid parsing errors.
  • API Authentication Errors: Make sure the API token credential is correctly configured and has sufficient permissions.
  • Incorrect Path Style: Selecting the wrong URL schema may cause 404 errors; verify the correct path style according to your API versioning.

Links and References

Discussion