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 quotes, configuration, pricing, admin, and MCP (a custom module). Specifically for the Configure resource and the ProductDetails operation, the node sends a JSON request body to the ScaleFluidly API endpoint corresponding to product details configuration. This enables retrieving or managing detailed product configuration data within workflows.

Common scenarios include:

  • Fetching detailed product information for configuration purposes.
  • Automating product setup or updates based on external system data.
  • Integrating product configuration steps into larger sales or inventory automation workflows.

Example use case:

  • A sales automation workflow that retrieves detailed product configuration data from ScaleFluidly to dynamically adjust quote line items or pricing rules.

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). Determines which ScaleFluidly instance the node interacts with.
Request JSON object representing the request body sent to the API. This contains all necessary parameters for the ProductDetails operation.

Output

The node outputs an array of JSON objects, each representing the response from the ScaleFluidly API for the executed operation. For the ProductDetails operation, the output JSON typically includes detailed product configuration data returned by the API.

If the API returns binary data (not indicated explicitly in this operation), it would be included in the binary output field; however, this operation primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if provided in input headers; otherwise, it attempts to use configured credentials.
  • No explicit internal credential names are exposed; users must configure appropriate API authentication tokens or credentials in n8n.
  • Network connectivity to the selected environment URL is required.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token and no credentials are configured, the node will throw an error. Ensure that either the input data includes a valid authorization token or proper API credentials are set up in n8n.
  • Operation not found error: If the specified operation (intent) does not match any known operation in the internal intent-to-URL map, the node will throw an error. Verify that the operation name is correct and supported.
  • API request failures: Network issues, invalid JSON in the request body, or incorrect environment URLs can cause request failures. Check the environment setting and validate the JSON request structure.
  • Empty or malformed response: Ensure the request body matches the expected schema for the ProductDetails operation to avoid unexpected API responses.

Links and References


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

Discussion