ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as quotes, configuration, pricing, admin, and MCP. Specifically, for the Configure resource and the Get User Favourite Products operation, the node fetches a list of products that a user has marked as favorites within the ScaleFluidly system.

Typical use cases include:

• Retrieving a user's favorite products to personalize product recommendations or dashboards.
• Syncing favorite product data into other systems or workflows.
• Displaying favorite products in custom UI components or reports.

For example, a sales automation workflow might use this node to pull a user's favorite products and then tailor offers or promotions accordingly.

Properties

The Request property is mandatory and must be provided as a JSON object. Its structure depends on the operation but generally includes filters or identifiers needed by the API endpoint.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation.

For the Get User Favourite Products operation, the output JSON typically contains details about each favorite product associated with the user, such as product IDs, names, categories, or other metadata as returned by the API.

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 endpoints corresponding to the selected environment.
• May require an API authentication token or bearer token passed via headers; the node attempts to extract this from input data or uses configured credentials.
• No explicit external libraries beyond standard n8n helpers and HTTP request utilities are used.

Troubleshooting

• Bearer token not found: If the authorization header with a bearer token is missing in the first input item and no stored authorization exists, the node will throw an error. Ensure the input data includes proper authorization headers or configure credentials correctly.
• Operation not found: If the specified operation does not match any known intent URL mapping, an error will occur. Verify the operation name is correct and supported.
• Invalid JSON in Request: The request_info parameter must be valid JSON. Malformed JSON will cause request failures.
• Environment URL issues: Selecting an incorrect environment or having network connectivity problems to the chosen URL can cause request failures.

Links and References

• ScaleFluidly API Documentation (QA environment)
• ScaleFluidly Developer Portal (Dev environment)

Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.