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 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 fulfillment services into workflows, automating product management, or performing custom API requests without needing separate HTTP request nodes.

Practical examples:

  • Automatically create new products in JTL-FFN from an e-commerce platform.
  • Update product details such as stock or pricing via workflow triggers.
  • Fetch product lists or specific product information for reporting or synchronization.
  • Perform custom API calls to other JTL-FFN 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., /api/fulfiller-v1/...)
- v1/role (e.g., /api/v1/fulfiller/...)
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), e.g., orders (only shown in Raw Request 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 for get, update, or delete operations (required in those cases).
Update-Methode HTTP method for updating a product:
PUT or PATCH (only 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 (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 data from the JTL-FFN API call. The exact structure depends on the called endpoint and operation:

  • For product operations, the output corresponds to product data returned by the API (e.g., product list, single product details).
  • For raw requests, the output reflects the 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 API access.
  • Uses an internal helper function to perform authenticated HTTP requests to the JTL-FFN API.
  • No additional external dependencies beyond standard n8n environment.

Troubleshooting

  • Common issues:

    • Incorrect API credentials or missing authentication token will cause authorization errors.
    • Invalid endpoint paths or HTTP methods may result in 404 or 405 HTTP errors.
    • Malformed JSON input for query, body, or headers can cause request failures.
    • Using product operations without required parameters (e.g., missing Product ID) 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 should be checked for details; ensure correct URL schema and parameters.

  • Resolution tips:

    • Double-check API token validity and permissions.
    • Validate JSON inputs using online tools before entering.
    • Confirm required parameters are provided for each operation.
    • Use Raw Request mode to test endpoints independently if product operations fail.

Links and References

Discussion