Overview
This node provides direct REST API access to the JTL-FFN Fulfiller v1 service, enabling users to perform various operations on products or make arbitrary REST calls. It supports two modes:
- Raw Request: Allows making any REST call by specifying HTTP method, endpoint path, query parameters, body, and headers.
- Products: Offers predefined product-related operations such as listing products, getting a product by ID, creating, updating, or deleting a product.
A typical use case is automating product management workflows in JTL-FFN, for example, deleting a product by its ID without manually interacting with the API. The node can also be used for custom API interactions beyond product management by using the raw mode.
Properties
| Name | Meaning |
|---|---|
| Modus | 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 to use (only shown in Raw mode): GET, POST, PUT, PATCH, DELETE. |
| Endpoint | Relative API path without leading slash (only shown in Raw mode), e.g., orders. |
| Operation | Product operation to perform (only shown in Products mode): - List Products - Get Product - Create Product - Update Product - Delete Product |
| Product ID | Identifier of the product to get, update, or delete (required for get, update, delete operations). |
| Update-Methode | HTTP method for updating a product (PUT or PATCH). Only relevant 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) | Query parameters as JSON object (shown if JSON Parameter is true). |
| Body (JSON) | Request body as JSON object (shown if JSON Parameter is true and operation is create or update). |
| Headers (JSON) | Additional HTTP headers as JSON object (shown if JSON Parameter is true). |
| Query-Parameter | Query parameters as UI key-value pairs (shown if JSON Parameter is false). |
| Body-Felder | Body fields as UI key-value pairs (shown if JSON Parameter is false and operation is create or update). |
| Zusätzliche Header | Additional HTTP headers as UI key-value pairs (shown if JSON Parameter is false). |
Output
The node outputs an array of JSON objects representing the response from the JTL-FFN API call. The exact structure depends on the API endpoint called and the operation performed. For example, when deleting a product, the output will typically contain confirmation or status information returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential for JTL-FFN API access.
- The node uses an internal helper function to send authenticated HTTP requests to the JTL-FFN Fulfiller v1 API.
- No additional external dependencies are required.
Troubleshooting
- Unknown Operation Error: If an unsupported product operation is selected, the node throws an error like
Unbekannte Operation: <operation>. Ensure the operation name matches one of the supported options. - Missing Required Parameters: Operations like "Get Product", "Update Product", and "Delete Product" 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 fields may cause request failures.
- API Authentication Errors: Ensure the API token credential is correctly configured and has sufficient permissions.
- Incorrect Path Style: Selecting the wrong URL schema might lead to 404 errors. Verify the correct path style according to your API setup.
Links and References
- JTL-FFN API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding REST call concepts