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 Get Available Product Group Options operation, the node fetches available product group options from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

  • Retrieving product group options to dynamically populate UI elements or decision logic in workflows.
  • Automating administrative tasks related to product group management.
  • Integrating ScaleFluidly product data into other systems or processes.

For example, a user might use this node to get all available product group options before assigning products to groups in an automated sales quoting process.

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 node interacts with.
Request A JSON object representing the request body sent to the API. Required for many operations but may be empty depending on the operation. For "Get Available Product Group Options," it can be used to specify filters or parameters if supported by the API.

Output

The node outputs an array of JSON objects under the json output field. Each object corresponds to the response from the ScaleFluidly API for the requested operation.

For the Get Available Product Group Options operation, the output will typically contain details about product group options available in the system, such as IDs, names, descriptions, or other metadata defined by the API.

If the API supports binary data responses for any operation, the node would handle them accordingly, but for this operation, the output is purely JSON.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • May require an API authentication token (bearer token) provided via input data headers or configured credentials.
  • No explicit external libraries beyond standard n8n workflow helpers are required.
  • The node expects the user to provide valid authorization either through input data headers or configured credentials.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no credential is configured, the node will throw an error. Ensure that the authorization token is correctly passed in the input data or set up proper API credentials.
  • Operation not found error: If the operation name does not match any known operation in the internal intent-to-URL mapping, the node will fail. Verify that the operation name is correct and supported.
  • API connectivity issues: Check the selected environment URL and network connectivity. Using the wrong environment or having firewall restrictions may cause request failures.
  • Invalid request body: If the JSON request body is malformed or missing required fields for the operation, the API may return errors. Validate the JSON structure before execution.

Links and References


Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.

Discussion