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 manually.
  • Products Mode: Offers predefined operations for managing products, including listing, retrieving, creating, updating, and deleting products.

This node is beneficial when integrating JTL-FFN Merchant functionalities into workflows, such as automating product management or custom API interactions without needing separate HTTP request nodes.

Practical examples:

  • Automatically create new products in the merchant system from an external inventory database.
  • Update product details like price or stock levels based on external triggers.
  • Fetch product lists or specific product information for reporting or synchronization.
  • Perform custom API calls to endpoints not covered by predefined operations.

Properties

Name Meaning
Modus Selects the mode of operation:
- Raw Request: Any REST call.
- Products: Predefined product-related operations.
Pfad-Stil URL schema style:
- role-v1 (e.g., merchant-v1): Produces URLs like /api/merchant-v1/....
- v1/role (e.g., v1/merchant): Produces URLs like /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). Required in Raw Request mode.
Operation Product operation to perform (shown in Products mode):
- List Products
- Get Product
- Create Product
- Update Product
- Delete Product
Product ID Identifier of the product for get, update, or delete operations. Required for these operations.
Update-Methode HTTP method used for updating a product:
PUT or PATCH. Only shown for product update operation.
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. Used if JSON Parameter is true.
Body (JSON) JSON object defining the request body. Used if JSON Parameter is true and operation is create or update product, or in raw mode.
Headers (JSON) JSON object defining additional HTTP headers. Used if JSON Parameter is true.
Query-Parameter Key-value pairs for query parameters. Used if JSON Parameter is false.
Body-Felder Key-value pairs for body fields. Used if JSON Parameter is false and operation is create or update product, or in raw mode.
Zusätzliche Header Key-value pairs for additional HTTP headers. Used if JSON Parameter is false.

Output

The node outputs an array of JSON objects representing the response data from the JTL-FFN Merchant API call.

  • For product operations, the output corresponds to the product data returned by the API (e.g., product list, single product details, confirmation of creation/update/deletion).
  • For raw requests, the output reflects the raw JSON response from the specified endpoint.

No binary data output is produced by this node.

Dependencies

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

Troubleshooting

  • Common issues:

    • Incorrect or missing API token credential will cause authentication failures.
    • Using an invalid endpoint or HTTP method in raw mode may result in API errors.
    • Providing malformed JSON in query/body/header fields can cause request failures.
    • Omitting required parameters like Product ID for product-specific operations will throw errors.

  • Error messages:

    • "Unbekannte Operation: <operation>": Indicates an unsupported product operation was selected; verify the operation name.
    • HTTP error responses from the API (e.g., 400 Bad Request, 401 Unauthorized) should be checked for correct credentials and parameter formatting.

  • Resolution tips:

    • Ensure the API token credential is correctly set up and valid.
    • Validate JSON inputs using external tools before entering them.
    • Double-check required parameters are provided for each operation.
    • Use the Raw Request mode to test endpoints manually if predefined operations fail.

Links and References

Discussion