ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

The ScaleFluidly 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 - Update Category operation, this node sends a request to update category details within the ScaleFluidly system.

This node is beneficial in scenarios where automated workflows need to manage or update categories programmatically, such as updating product categories, pricebook associations, or discounts in an e-commerce or sales platform integrated with ScaleFluidly.

Practical example:
A user can automate the process of updating category information based on changes in inventory or pricing strategies by sending structured JSON requests through this node, eliminating manual updates in the ScaleFluidly dashboard.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server).
Request The JSON-formatted request body containing the data to update the category. This must conform to the expected API schema for the update category operation.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each JSON object contains the API response data corresponding to the update category request.

If the API returns binary data (not typical for this operation), it would be included accordingly, but primarily the output is JSON reflecting success, failure, or detailed information about the updated category.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • May require an API authentication token (bearer token) provided via HTTP headers; the node expects this token to be present in the first input item's JSON under headers.authorization.
  • No explicit internal credential names are exposed; users must configure appropriate API credentials or tokens externally.

Troubleshooting

  • Bearer token not found error: If the authorization token is missing from the first input's headers, the node will throw an error. Ensure that the first input item includes a valid bearer token in json.headers.authorization.
  • Operation not found error: If the operation name does not map to a known API endpoint, the node will report this. Verify that the operation parameter is correctly set to "update_category" under the Admin resource.
  • Invalid request body: Since the request body is user-provided JSON, malformed or incomplete data may cause API errors. Validate the JSON structure against ScaleFluidly's API documentation before execution.
  • Environment URL issues: Selecting an incorrect environment or having network connectivity problems to the specified URL can cause request failures.

Links and References


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

Discussion