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. This mode is useful for advanced users who want full control over the API requests beyond predefined operations.
Products Mode: Offers predefined product-related operations such as listing products, retrieving a single product by ID, creating, updating, or deleting products. This simplifies common product management tasks without needing to manually construct API requests.
Typical use cases include synchronizing product data between JTL-FFN and other systems, automating product catalog updates, or integrating custom workflows that require direct API access.
Example scenarios:
- Automatically fetch all products from the merchant system to update an external inventory database.
- Create new products in bulk by providing product details through the node.
- Update specific product information based on changes detected elsewhere.
- Delete obsolete products programmatically.
Properties
| Name | Meaning |
|---|---|
| Modus (mode) | Selects the request mode: - Raw Request: Any REST call. - Products: Predefined product operations (list, get, create, update, delete). |
| Pfad-Stil (pathStyle) | URL schema style: - role-v1: e.g., /api/merchant-v1/...- v1/role: e.g., /api/v1/merchant/... |
| Methode (method) | 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 only in Products mode): - List Products - Get Product - Create Product - Update Product - Delete Product |
| Product ID | ID of the product to get, update, or delete. Required for get, update, and delete operations in Products mode. |
| Update-Methode | HTTP method for updating a product (PUT or PATCH). Shown only when updating a product in Products mode. |
| JSON Parameter | Whether to define query, body, and headers as JSON objects (true) or via UI key-value pairs (false). Applies to both modes. |
| 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 applicable (e.g., create/update product). |
| Headers (JSON) | JSON object defining additional HTTP headers. Used if JSON Parameter is true. |
| Query-Parameter | Key-value pairs for query parameters if JSON Parameter is false. |
| Body-Felder | Key-value pairs for body fields if JSON Parameter is false and applicable (create/update product). |
| Zusätzliche Header | Key-value pairs for additional HTTP headers if JSON Parameter is false. |
Output
The node outputs an array of JSON objects representing the response data from the JTL-FFN Merchant API.
- In Products mode, the output corresponds to product data returned by the API, such as lists of products or individual product details.
- In Raw Request mode, the output reflects the raw JSON response from the specified API endpoint.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential for the JTL-FFN Merchant API.
- The node uses an internal transport/request helper to perform authenticated HTTP requests.
- No additional external dependencies are required beyond proper API credentials and network access to the JTL-FFN Merchant API endpoints.
Troubleshooting
- Unknown Operation Error: If an unsupported product operation is selected, the node throws an error indicating "Unbekannte Operation". Ensure the operation name matches one of the supported 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, malformed JSON in query, body, or headers fields can cause errors. Validate JSON syntax before execution.
- Authentication Failures: Ensure the API token credential is correctly configured and has sufficient permissions.
- Incorrect Path Style: Selecting the wrong URL schema may lead to 404 errors. Verify the correct path style according to your API version and setup.
Links and References
- JTL-FFN Merchant API Documentation (general reference for API endpoints and usage)
- n8n documentation on HTTP Request Node for understanding REST API interactions
- JSON validation tools such as JSONLint for verifying JSON input correctness