ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as Admin, Quote, Configure, Pricing, MCP, and Product. Specifically, for the Admin resource and the Get All Product Attributes operation, it fetches all product attribute data from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

• Retrieving comprehensive product attribute information for inventory or catalog management.
• Automating synchronization of product attributes between ScaleFluidly and other systems.
• Supporting dynamic UI elements that depend on product attribute metadata.

For example, a user might use this node to pull all product attributes before updating a product catalog in an e-commerce platform or to analyze product features for reporting purposes.

Properties

The node also requires selecting the Resource (admin) and Operation (get_all_product_attributes), but these are fixed by your provided context.

Output

The node outputs an array of JSON objects under the json output field. Each object corresponds to the response from the ScaleFluidly API for the requested operation. For the "Get All Product Attributes" operation, the output will contain detailed product attribute data, typically including attribute names, types, possible values, and related metadata.

No binary data output is indicated for this operation.

Dependencies

• Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
• May require an authorization token passed via HTTP headers; the node expects a bearer token either from input data headers or from configured credentials.
• The node uses an internal mapping of operations to URLs and HTTP methods to construct requests.
• No explicit external libraries beyond standard n8n workflow helpers are used.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no credential is configured, the node will throw an error. Ensure that the authorization token is provided either in the input data headers or through the node’s credential configuration.
• Operation not found error: If the specified operation is not recognized in the internal intent-to-URL map, the node will fail. Verify that the operation name matches one of the supported operations exactly.
• API request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request failures. Check connectivity and authentication details.
• Invalid or missing request body: Some operations may require a JSON request body. Make sure to provide valid JSON if needed.

Links and References

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

Note: Replace environment URLs accordingly based on your deployment.