ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API
Join our community

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 Attributes operation, the node fetches attributes related to product groups available in the system.

Common scenarios where this node is beneficial include:

  • Retrieving metadata about product group attributes to dynamically build user interfaces or validate data.
  • Automating administrative tasks that require knowledge of product group attribute configurations.
  • Integrating ScaleFluidly's product group data into other workflows or systems for enhanced automation.

For example, a user might use this node to get all available attributes for product groups before creating or updating product configurations in an automated sales process.

Properties

Name Meaning
Environment The environment URL to target: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), or 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 Attributes," it can typically be empty or contain filters 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 Attributes operation, the output JSON will contain details about the product group attributes available in the system, such as attribute names, types, possible values, and other metadata relevant to product grouping.

The node does not output binary data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the selected environment.
  • Optionally uses an API authentication token (Bearer token) passed via the input data headers or through configured credentials.
  • No explicit external libraries beyond n8n core helpers are required.
  • The node expects the user to provide valid authorization either in the input data or via n8n credentials configuration.

Troubleshooting

  • Bearer token not found: 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 provided either in the input data headers or configured properly in n8n credentials.
  • Operation not found: If the operation name does not match any known operation in the internal intent-to-URL mapping, the node will throw an error indicating the operation was not found. Verify the operation name is correct and supported.
  • API request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request failures. Check connectivity, environment selection, and token validity.
  • Malformed JSON in Request property: The request_info property must be valid JSON. Invalid JSON will cause errors when sending the request.

Links and References

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

Discussion