JTL-FFN (Fulfiller v1)

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

Actions5

Overview

This node provides direct REST API access to the JTL-FFN Fulfiller v1 service, enabling users to perform various operations related to products or arbitrary REST calls. It supports two main modes:

  • Raw Request: Allows making any custom REST API call by specifying HTTP method, endpoint, query parameters, body, and headers.
  • Products: Offers predefined product-related operations such as listing products, retrieving a single product by ID, creating, updating, or deleting a product.

This node is beneficial when integrating JTL fulfillment services into workflows, automating product management, or extending functionality with custom API calls.

Practical examples:

  • Automatically fetch product details from JTL fulfillment for order processing.
  • Create or update product information in JTL fulfillment based on external data sources.
  • Perform custom API requests to endpoints not covered by predefined operations.

Properties

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

Output

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

  • For product operations, it returns product data such as product details, lists, or confirmation of creation/update/deletion.
  • For raw requests, it returns whatever JSON data the specified endpoint responds with.

No binary data output is indicated.

Dependencies

  • Requires an API authentication token credential for JTL-FFN API access.
  • Uses an internal helper function to make authenticated HTTP requests to the JTL-FFN API.
  • No additional external dependencies are required beyond standard n8n environment and the configured API token.

Troubleshooting

  • Common issues:

    • Missing or invalid API token will cause authentication failures.
    • Incorrect endpoint paths or HTTP methods may result in 404 or 405 errors.
    • Providing malformed JSON in parameters can cause request failures.
    • Using product operations without specifying a valid Product ID (for get, update, delete) will throw errors.

  • Error messages:

    • Unbekannte Operation: <operation>: Indicates an unsupported product operation was selected; verify the operation name.
    • HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) should be checked against credentials and endpoint correctness.

  • Resolution tips:

    • Ensure the API token credential is correctly set up.
    • Double-check the selected mode and operation match the intended use.
    • Validate JSON inputs or switch to UI key-value input if unsure.
    • Confirm that required fields like Product ID are provided when needed.

Links and References

Discussion