ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

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 Add Products to Category operation, the node sends a request to add one or more products to a specified category within the ScaleFluidly system.

Typical use cases include automating product categorization workflows in sales or inventory management systems, where products need to be programmatically assigned to categories based on business logic or external triggers. For example, after importing new products into a catalog, this node can be used to assign those products to relevant categories automatically.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server).
Request JSON object representing the request body sent to the API. This contains details such as product IDs and category information required to add products to a category.

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed. Each JSON object represents the API response for the "Add Products to Category" operation, typically including confirmation of success, updated category details, or error messages if the operation failed.

If the API supports binary data in responses, it is not explicitly handled or output by this node based on the provided code.

Dependencies

  • Requires access to the ScaleFluidly API endpoint, which varies depending on the selected environment (Dev, QA, or Local).
  • Optionally uses an API authentication token (Bearer token) passed via HTTP headers. If no explicit token is provided in the first input item's headers, the node will throw an error.
  • No other external dependencies are indicated.

Troubleshooting

  • Bearer token not found: The node expects an authorization token in the headers of the first input item. If missing, it throws an error. Ensure that the first input includes a valid Bearer token in its headers.authorization field.
  • Operation not found: If the specified operation does not match any known intent URL mapping, the node throws an error indicating the operation is invalid. Verify the operation name matches supported actions.
  • API request failures: Network issues, incorrect environment URLs, or malformed request bodies may cause API errors. Check the environment setting and ensure the JSON request body is correctly structured according to ScaleFluidly API specifications.

Links and References


Note: The exact structure of the request JSON and response depends on the ScaleFluidly API schema, which should be referenced in the official documentation.

Discussion