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 freely. This mode is useful for custom or less common API calls not covered by predefined operations.
  • Products: Offers predefined product-related operations such as listing products, getting a single product by ID, creating, updating, or deleting a product. This simplifies common product management tasks.

Typical use cases include integrating JTL-FFN product data into workflows, automating product updates, or extending functionality with custom API requests.

Properties

Name Meaning
Modus Selects the mode of operation: "Raw Request" for arbitrary REST calls or "Products" for predefined product operations.
Pfad-Stil URL schema style for API paths: "role-v1" results in /api/merchant-v1/..., "v1/role" results in /api/v1/merchant/....
Methode HTTP method to use (GET, POST, PUT, PATCH, DELETE) — shown only in Raw Request mode.
Endpoint Relative API path without leading slash, e.g., products — used only in Raw Request mode.
Operation Product operation to perform: List Products, Get Product, Create Product, Update Product, Delete Product — shown only in Products mode.
Product ID Identifier of the product to get, update, or delete — required for those operations in Products mode.
Update-Methode HTTP method for updating a product: PUT or PATCH — shown only 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 — shown if JSON Parameter is true and operation is create or update.
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. The exact structure depends on the API endpoint and operation performed. For example:

  • Listing products returns an array of product objects.
  • Getting a product returns a single product object.
  • Creating, updating, or deleting a product returns the API's confirmation or updated product data.

No binary data output is produced by this node.

Dependencies

  • Requires an API authentication token credential for JTL-FFN Merchant v1.
  • Uses an internal helper function to send HTTP requests to the JTL-FFN Merchant API.
  • No additional external dependencies beyond standard HTTP and JSON handling.

Troubleshooting

  • Unknown Operation Error: If an unsupported product operation is selected, the node throws an error indicating the unknown operation. Ensure the operation name matches one of the supported options.
  • Missing Required Parameters: Operations like get, update, and delete require a valid Product ID. Omitting it will cause errors.
  • Invalid JSON Input: When using JSON parameter mode, malformed JSON in query, body, or headers will cause parsing errors.
  • API Authentication Errors: Ensure the API token credential is correctly configured and has sufficient permissions.
  • Incorrect Path Style: Selecting the wrong URL schema may lead to 404 errors; verify the correct path style for your API version.

Links and References

Discussion