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

Typical use cases include:

  • Updating product measurement conversions in a centralized product catalog.
  • Automating adjustments to product units when integrating with other systems or workflows.
  • Managing product data consistency across sales, inventory, and pricing modules.

For example, a user might update the conversion rate between different units (e.g., from kilograms to pounds) for a product to ensure accurate pricing and inventory tracking.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev, QA, Local. Determines the base API URL.
Request JSON object containing the request body specific to the operation. This includes the data needed to edit the product UOM conversion.

The Request property must be provided as a JSON object that contains all necessary fields required by the ScaleFluidly API to perform the "edit product UOM conversion" action. The exact structure depends on the API specification but typically includes identifiers and conversion parameters.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed.

  • The json output field contains the parsed JSON response from the API call corresponding to the edit operation.
  • There is no indication that binary data is returned or handled by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • Optionally uses an API authentication token if provided in the input data headers or via configured credentials.
  • No explicit external libraries beyond standard n8n workflow helpers are used.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no prior token was stored, the node will throw an error. Ensure the input data includes valid authorization headers or configure credentials properly.
  • Operation not found: If the operation name does not map to a known intent URL, the node throws an error indicating the operation is invalid. Verify the operation name matches supported actions.
  • Invalid JSON in Request: The request_info property must be valid JSON. Malformed JSON will cause the API call to fail.
  • API connectivity issues: Network problems or incorrect environment URLs can cause request failures. Confirm the environment URL is reachable and correct.

Links and References

Note: Replace these links with actual documentation URLs relevant to your deployment if different.

Discussion