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, MCP, and Product. Specifically, for the Admin resource and the Add Product UOM (Unit of Measure) operation, the node sends a request to add a new product unit of measure in the ScaleFluidly system.

Typical use cases include automating product management workflows where units of measure need to be added programmatically, such as when onboarding new products or updating product catalogs in bulk. For example, a user might add a new "box" or "pack" unit to a product to support different packaging options.

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 containing the request body for the API call. This should include all necessary data to add the product UOM according to ScaleFluidly API specifications.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each JSON object corresponds to the API response for the respective request made to add a product UOM.

  • The json output field contains the parsed JSON response from the API.
  • If the API returns binary data (not typical for this operation), it would be included accordingly, but this operation primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token if provided in the input data headers; otherwise, it attempts to use credentials configured in n8n under a generic API key credential.
  • No other external dependencies are required.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token and no API credentials are configured, the node will throw an error. Ensure that either the input includes a valid authorization token or the node has proper API credentials set up.
  • Operation not found error: If the specified operation (intent) does not match any known operation URL mapping, the node will throw an error indicating the operation was not found. Verify that the operation name is correct and supported.
  • Invalid request body: Since the request body is user-provided JSON, malformed or incomplete JSON may cause API errors. Validate the JSON structure before running the node.
  • Environment URL issues: Selecting an incorrect environment or having network connectivity issues to the chosen environment URL can cause request failures.

Links and References


This summary focuses on the Admin resource and the Add Product UOM operation based on the provided properties and source code analysis.

Discussion