ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as Admin, Quote, Configure, Pricing, and MCP. Specifically, for the Admin resource with the Get Categories operation, the node fetches category-related data from the ScaleFluidly backend.

Typical use cases include:

• Retrieving administrative category information for managing or displaying categories in workflows.
• Automating category data retrieval to synchronize with other systems or dashboards.
• Using category data as part of larger automation processes involving product or pricing configurations.

For example, a user might configure this node to pull all categories from the admin environment to update a product catalog or to audit category settings regularly.

Properties

The node also requires selecting:

• Resource: fixed to "Admin" for this operation.
• Operation: fixed to "Get Categories" (part of adminActions).
• Request Body: JSON input for request details if needed (optional depending on operation specifics).

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. Each item in the output corresponds to one API response per input item processed.

The json output field contains the parsed JSON response from the API, typically including category data structures such as category IDs, names, descriptions, and related metadata.

If the API returns binary data (not typical for this operation), it would be included in the binary output field, but this operation primarily deals with JSON data.

Dependencies

• Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
• Optionally uses an API authentication token passed via HTTP Authorization header. This token must be provided in the input data headers or through configured credentials.
• No explicit external libraries beyond n8n's standard HTTP request helpers are required.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization token in its headers, and no prior token is stored, the node will throw an error. Ensure that the input data includes a valid bearer token in the authorization header or that credentials are properly configured.
• Operation not found error: If the specified operation is not mapped in the internal intent-to-URL map, the node will fail. Verify that the operation name matches exactly and is supported.
• API connectivity issues: Check network access to the selected environment URL and ensure the API service is reachable.
• Invalid JSON in request body: If the request_info parameter contains malformed JSON, the API call may fail. Validate JSON syntax before execution.

Links and References

• ScaleFluidly API Documentation (QA environment)
• n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/