ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

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 Product UOM Conversion operation, it enables adding a unit of measure (UOM) conversion for products within the ScaleFluidly system.

Typical use cases include automating product data management workflows where unit conversions are necessary, such as converting quantities between different measurement units in inventory or pricing systems. For example, a user might add a conversion factor from kilograms to pounds for a product to ensure consistent calculations across different regions or sales channels.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). This determines which ScaleFluidly instance the request is sent to.
Request JSON object representing the request body payload required by the "Add Product UOM Conversion" operation. This contains the details of the UOM conversion to be added. It must be provided in valid JSON format.

Output

The node outputs an array of JSON objects corresponding to the responses received from the ScaleFluidly API for each input item processed. Each JSON object represents the result of the API call for adding a product UOM conversion, typically including confirmation details or the created resource's data.

If the API supports binary data in responses, this node would handle it accordingly, but based on the static analysis, the output is primarily JSON structured data reflecting the API response.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the selected environment.
  • May require an API authentication token (bearer token) passed via HTTP headers. The node expects this token to be present in the input data's headers.authorization field on the first item or managed internally through n8n credentials if configured.
  • No explicit external libraries beyond standard n8n workflow helpers and request utilities are needed.

Troubleshooting

  • Bearer token not found error: If the authorization token is missing from the input data headers and no internal credential is set, the node will throw an error. Ensure that the bearer token is correctly supplied either in the input data or configured in the node credentials.
  • Operation not found error: If the operation name does not match any known intent URL mapping, the node will raise an error indicating the operation is invalid. Verify that the operation parameter is correctly set to "add_product_uom_conversion" for this use case.
  • Invalid JSON in Request property: Since the request body is expected as JSON, malformed JSON will cause the API call to fail. Validate the JSON structure before running the node.
  • API endpoint unreachable: Selecting an incorrect environment URL or network issues may prevent successful API calls. Confirm the environment URL and network connectivity.

Links and References


This summary focuses on the Admin resource's Add Product UOM Conversion operation as requested, based on static code analysis of the bundled source and provided properties.

Discussion