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 flexible interaction with its endpoints. It supports two main modes:

  • Raw Request: Allows users to perform arbitrary REST calls by specifying HTTP method, endpoint path, query parameters, body, and headers.
  • Products: Offers predefined operations for managing products, such as listing all products, retrieving a single product by ID, creating, updating, or deleting a product.

Typical use cases include integrating JTL-FFN fulfillment services into workflows for inventory management, order processing, or product catalog synchronization. For example, you can list all products in your inventory, update product details, or execute custom API calls to other endpoints not covered by predefined operations.

Properties

Name Meaning
Modus (mode) Selects the mode of operation:
- Raw Request: Any REST call.
- Products: Predefined product-related operations.
Pfad-Stil (pathStyle) URL schema style:
- role-v1: e.g., /api/fulfiller-v1/...
- v1/role: e.g., /api/v1/fulfiller/...
Methode (method) HTTP method for raw requests:
GET, POST, PUT, PATCH, DELETE. Only shown when mode is "Raw Request".
Endpoint Relative API path without leading slash for raw requests (e.g., orders). Required when mode is "Raw Request".
Operation Product operation to perform when mode is "Products":
- 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 via 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 involves sending a body (create/update).
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 involves sending a body (create/update).
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 from the JTL-FFN API call. The structure depends on the specific endpoint and operation invoked:

  • For List Products, the output is typically a list of product objects with their details.
  • For Get Product, a single product object is returned.
  • For create, update, or delete operations, the output reflects the API's response confirming the action.

No binary data output is produced by this node.

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 external libraries beyond those bundled with n8n are required.

Troubleshooting

  • Error: Unknown Operation — This occurs if an unsupported product operation is selected. Ensure the operation name matches one of the predefined options.
  • Missing Required Parameters — For product operations like get, update, or delete, the product ID must be provided; otherwise, the request will fail.
  • Invalid JSON Input — When using JSON parameter mode, ensure that the JSON syntax for query, body, and headers is correct to avoid parsing errors.
  • Authentication Errors — Verify that the API token credential is correctly configured and has sufficient permissions.
  • Incorrect Endpoint or Path Style — When using raw mode, ensure the endpoint path and path style match the API specification to avoid 404 or routing errors.

Links and References

Discussion