JTL-FFN (Any v1)

Direkter REST-Zugriff auf JTL-FFN Any v1
Join our community

Overview

This node provides direct REST API access to the "JTL-FFN Any v1" service, allowing users to perform arbitrary HTTP requests (GET, POST, PUT, PATCH, DELETE) against endpoints under the "any-v1" API path. It is designed for flexible integration scenarios where custom or less common API calls are needed beyond predefined operations.

Typical use cases include:

  • Accessing specific resources or endpoints in the JTL-FFN system that are not covered by other dedicated nodes.
  • Performing custom queries or updates with dynamic query parameters, request bodies, and headers.
  • Quickly testing or prototyping API interactions without writing separate code.

For example, a user might:

  • Send a GET request to retrieve shipment data from /api/any-v1/shipments.
  • Post JSON data to create or update records on a custom endpoint.
  • Use different URL path styles depending on API versioning preferences.

Properties

Name Meaning
Pfad-Stil URL schema style:
- role-v1 results in paths like /api/any-v1/...
- v1/role results in /api/v1/any/...
Methode HTTP method to use for the request: GET, POST, PUT, PATCH, or DELETE
Endpoint Relative path under any-v1 without leading slash, e.g., shipments. Required
JSON Parameter Whether to define Query, Body, and Headers as raw JSON (true) or as UI key-value pairs (false)
Query (JSON) JSON object defining query parameters when JSON Parameter is true
Body (JSON) JSON object defining the request body when JSON Parameter is true
Headers (JSON) JSON object defining additional headers when JSON Parameter is true
Query-Parameter Key-value pairs for query parameters when JSON Parameter is false
Body-Felder Key-value pairs for body fields when JSON Parameter is false
Zusätzliche Header Key-value pairs for additional headers when JSON Parameter is false

Output

The node outputs an array of JSON objects representing the parsed response from the API call. Each item corresponds to one element of the returned data, converted into JSON format suitable for further processing in n8n workflows.

If the API returns binary data, it is not explicitly handled or output by this node; only JSON responses are processed.

Dependencies

  • Requires an API authentication token credential for the JTL-FFN API.
  • Uses an internal helper function to make HTTP requests to the JTL-FFN Any v1 endpoints.
  • No external libraries beyond those bundled with n8n are required.

Troubleshooting

  • Invalid Endpoint or Path Style: Ensure the Endpoint property is correctly specified without a leading slash and matches the expected API resource. Choose the correct Pfad-Stil matching your API versioning scheme.
  • Malformed JSON Parameters: When using JSON input for query, body, or headers, ensure valid JSON syntax to avoid parsing errors.
  • Authentication Errors: Verify that the API token credential is correctly configured and has sufficient permissions.
  • Unexpected Response Format: The node expects JSON responses; if the API returns non-JSON data, the node may fail or produce empty output.
  • Empty or Missing Data: Check that the API endpoint actually returns data for the given request parameters.

Links and References

Discussion