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 and the Update Option Group operation, it enables updating option groups within the ScaleFluidly system by sending a custom JSON request body to the appropriate API endpoint.

Common scenarios where this node is beneficial include automating administrative updates in ScaleFluidly, such as modifying configuration option groups without manual API calls. For example, an admin could update product option groups dynamically based on business rules or external triggers, streamlining configuration management.

Properties

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed. Each output JSON object contains the API response data resulting from the update operation on the option group.

If the API returns binary data (not indicated explicitly here), it would be included accordingly, but primarily the output is JSON structured data reflecting the updated state or confirmation from the ScaleFluidly service.

Dependencies

• Requires access to the ScaleFluidly API endpoints.
• Optionally uses an API authentication token if provided in the input data headers under authorization.
• No explicit internal credential names are exposed; users must configure an API key or token as per their ScaleFluidly API setup.
• The node supports three environments (Dev, QA, Local) selectable via the Environment property.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no static authorization header was previously set, the node will throw an error. Ensure that the input JSON includes a valid authorization token or configure credentials properly.
• Operation not found error: If the specified operation (intent) does not match any known operation URL mapping, the node throws an error indicating the operation is not found. Verify the operation name matches supported actions.
• Invalid request body: Since the request body is user-provided JSON, malformed or incorrect data may cause API errors. Validate the JSON structure against ScaleFluidly API documentation before execution.
• Environment URL issues: Selecting an incorrect environment or having network connectivity problems to the chosen environment URL can cause request failures.

Links and References

• ScaleFluidly API Documentation (QA environment URL)
• Refer to ScaleFluidly API docs for detailed schemas and examples of the "update_option_group" request body format.