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 Product Attributes operation, it enables retrieval of product attribute data from the ScaleFluidly system.

Typical use cases include:

  • Fetching detailed attributes of products managed within ScaleFluidly for further processing or reporting.
  • Integrating product attribute data into workflows that require dynamic product information.
  • Automating administrative tasks related to product metadata management.

For example, a user might use this node to get all attributes associated with a specific product group to dynamically build product configuration interfaces or validate product data in an automated sales process.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local.
Request JSON object containing the request body parameters required by the API for the operation.

Details:

  • Environment: Selects which ScaleFluidly API environment to interact with.
  • Request: A JSON input that contains the necessary parameters for the API call. This is required and varies depending on the operation; for "Get Product Attributes," it would typically specify identifiers or filters needed by the API endpoint.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Product Attributes" operation, the output JSON will contain product attribute details as returned by the API.

If the API returns binary data (not typical for this operation), the node would handle it accordingly, but based on the static code and operation context, the output is primarily JSON structured data.

Dependencies

  • Requires access to the ScaleFluidly API endpoints specified by the selected environment.
  • Optionally uses an API authentication token passed via HTTP headers (Bearer token) if provided in the input data.
  • No explicit internal credential type names are exposed; users must configure appropriate API authentication credentials in n8n if needed.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no prior token was stored, the node throws an error. Ensure that the input data includes valid authorization headers or that credentials are properly configured.
  • Operation not found error: If the specified operation or intent name does not match any known mapping, the node will throw an error indicating the operation is not found. Verify the operation name matches one of the supported actions.
  • Invalid JSON in Request property: Since the request body is expected as JSON, malformed JSON input can cause failures. Validate JSON syntax before running the node.
  • API connectivity issues: Network problems or incorrect environment URLs can lead to request failures. Confirm the environment URL is reachable and correct.

Links and References


This summary focuses on the Admin resource's Get Product Attributes operation, describing its purpose, inputs, outputs, and common considerations based on the provided source code and properties.

Discussion