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

Typical use cases include:

  • Retrieving configurable product options to dynamically build product configurations.
  • Automating product option lookups in sales or inventory workflows.
  • Integrating product option data into larger automation pipelines for quoting or order management.

For example, a sales automation workflow could use this node to fetch all available options for a product before generating a quote, ensuring that only valid options are presented to customers.

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 JSON object representing the request body sent to the API. Required for most operations including this one. It contains parameters specific to the "Get Available Product Options" operation.

Output

The node outputs an array of JSON objects corresponding to the API response for the requested operation. For the "Get Available Product Options" operation, the output JSON typically includes details about product options available in the system, such as option IDs, names, values, and possibly grouping or attribute information.

If the API returns binary data (not typical for this operation), it would be included accordingly, but this operation primarily deals with JSON data describing product options.

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.
  • The node uses an internal mapping of operation names to API endpoints and HTTP methods.
  • No explicit external npm packages beyond n8n core dependencies are required.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a Bearer token, and no other authorization is set, the node will throw an error. Ensure the API token is correctly passed in the input or configured in credentials.
  • Operation not found: If the operation name does not match any known intent URL mapping, the node throws an error indicating the operation is invalid. Verify the operation name is correct and supported.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause API errors. Check the environment URL, request JSON structure, and API token validity.
  • Empty or malformed request_info: Since the request body is required, ensure it is properly formatted JSON matching the expected schema for the operation.

Links and References


This summary focuses on the Admin resource's Get Available Product Options operation based on the provided source code and property definitions.

Discussion