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. This mode is useful for advanced users who want full control over the API requests.
Products Mode: Offers predefined operations specifically for managing products, such as listing all products, retrieving a single product by ID, creating new products, updating existing products, or deleting products. This simplifies common product-related tasks without needing to manually construct API requests.
Typical use cases include automating product management workflows in e-commerce systems integrated with JTL-FFN, or performing custom API calls to other fulfiller endpoints not covered by predefined operations.
Example scenarios:
- Automatically update product details based on inventory changes.
- Retrieve product information to synchronize with another system.
- Create new products programmatically from external data sources.
- Execute custom API calls to non-product endpoints using raw mode.
Properties
| Name | Meaning |
|---|---|
| Modus | Selects the request mode: • Raw Request — arbitrary 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 (only shown in Raw Request mode) |
| Endpoint | Relative API path for raw requests (without leading slash), e.g., orders (required in Raw Request mode) |
| Operation | Product operation to perform (only 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 in Products mode) |
| Update-Methode | HTTP method used for updating a product: PUT or PATCH (only for Update Product operation in Products mode) |
| 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 (used if JSON Parameter is true) |
| Body (JSON) | JSON object defining the request body (used if JSON Parameter is true and operation is create or 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 is create or 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 data from the JTL-FFN API call. The exact structure depends on the endpoint and operation performed:
- For product operations, the output contains product data such as product details, lists, or confirmation of creation/update/deletion.
- For raw requests, the output reflects the raw JSON response returned by the specified API 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 fulfiller API.
- No additional external dependencies beyond standard n8n environment and configured credentials.
Troubleshooting
- Error: Unknown Operation — Occurs if an unsupported product operation is selected. Verify that the operation name matches one of the predefined options.
- Missing Required Parameters — Ensure required fields like Product ID (for get/update/delete) or Endpoint (for raw mode) are provided.
- Authentication Errors — Confirm that a valid API token credential is configured and has sufficient permissions.
- Invalid JSON Input — When using JSON parameter mode, ensure that the JSON syntax for query, body, and headers is correct.
- Unexpected API Responses — Check the API documentation for correct endpoint usage and parameter formats; enable raw mode for debugging custom requests.
Links and References
- JTL-FFN API Documentation (general reference for API endpoints and usage)
- n8n Documentation on Creating Custom Nodes
- REST API concepts: HTTP Methods