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 Get All Product UOMs operation, it fetches all product units of measure (UOMs) from the ScaleFluidly system.

This node is beneficial in scenarios where you need to retrieve standardized measurement units for products, which can be used for inventory management, pricing calculations, or product configuration workflows. For example, a user might want to list all available UOMs to populate dropdowns in a product catalog or validate input data against supported units.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: "Dev", "QA", "Local".
  • Environment selects the base URL for the API endpoint depending on the deployment stage or local testing.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get All Product UOMs" operation, the output JSON typically contains a list of product unit of measure records, each describing a unit's attributes such as name, abbreviation, conversion factors, or other metadata defined by 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.

Example output structure (simplified):

[
  {
    "id": "uom_001",
    "name": "Kilogram",
    "abbreviation": "kg",
    "conversionFactor": 1,
    "description": "Standard unit of mass"
  },
  {
    "id": "uom_002",
    "name": "Gram",
    "abbreviation": "g",
    "conversionFactor": 0.001,
    "description": "One thousandth of a kilogram"
  }
]

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Needs an authorization token passed via HTTP headers (Bearer token). This token must be provided in the input data's headers.authorization field on the first item or managed through n8n credentials if configured.
  • The node supports three environment URLs (Dev, QA, Local) selectable via the Environment property.
  • No additional external libraries beyond standard n8n helpers are required.

Troubleshooting

  • Bearer token not found error: If the authorization header is missing in the first input item, 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 specified operation does not exist in the internal intent-to-URL mapping, the node will fail. Verify that the operation name matches one of the supported operations for the Admin resource.
  • API request failures: Network issues, invalid tokens, or incorrect environment URLs may cause request errors. Check connectivity, token validity, and environment selection.
  • Empty or malformed response: Confirm that the API endpoint is returning expected data and that the request body (if any) is correctly formatted.

Links and References

Discussion