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 All Categories operation, it fetches all category data from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

• Retrieving a list of all categories for administrative or reporting purposes.
• Synchronizing category data between ScaleFluidly and other systems.
• Automating workflows that depend on up-to-date category information.

For example, an admin user might use this node to pull all product categories before updating pricing rules or managing product groupings.

Properties

The Environment property determines which ScaleFluidly API endpoint the node will communicate with:

• Dev: Development environment URL.
• QA: Quality Assurance environment URL.
• Local: Localhost URL for local testing.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get All Categories" operation under the Admin resource, the output JSON contains the list of all categories retrieved from the API.

The exact structure depends on the ScaleFluidly API response but typically includes fields describing each category's attributes (e.g., ID, name, description).

No binary data output is produced by this node.

Dependencies

• Requires access to the ScaleFluidly API endpoints specified by the chosen environment.
• Optionally uses an API authentication token passed via the HTTP Authorization header. This token must be provided in the input data headers or through configured credentials.
• No explicit internal credential names are exposed; users must supply a valid bearer token for authorization.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization token in its headers, and no static authorization header was previously set, the node throws an error. Ensure that the input data includes a valid bearer token in the authorization header or configure credentials properly.
• Operation not found error: If the specified operation is not mapped in the internal intent-to-URL map, the node will throw an error indicating the operation is unknown. Verify the operation name matches one of the supported operations.
• API request failures: Network issues, invalid tokens, or incorrect environment URLs can cause request failures. Check connectivity, token validity, and environment selection.

Links and References

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

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