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 Product Recommendations operation, the node sends a JSON request body to the ScaleFluidly API endpoint corresponding to product recommendations and returns the API response.

Typical use cases include:

  • Fetching product recommendations based on specific criteria or configurations.
  • Automating product configuration workflows by integrating ScaleFluidly's recommendation engine.
  • Enhancing sales or quoting processes by dynamically retrieving recommended products.

For example, a user might input customer preferences or current quote details in the request body, and the node will return recommended products that best fit those inputs.

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 API instance to interact with.
Request A JSON object representing the request body sent to the ScaleFluidly API. This contains all necessary parameters for the product recommendations operation.

Output

The node outputs an array of JSON objects under the json field. Each object corresponds to the response from the ScaleFluidly API for the given request. The structure depends on the API's response format for product recommendations, typically including recommended product details, scores, or related metadata.

If the API returns binary data (not indicated in this code), it would be included accordingly, but this node primarily handles JSON responses.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if provided in the input data headers; otherwise, it attempts to use credentials configured in n8n under a generic API key credential.
  • No other external dependencies are required beyond standard HTTP request capabilities provided by n8n.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token and no API credential is configured, the node throws an error. Ensure that either the input includes a valid authorization header or the node has proper API credentials set up.
  • Operation not found: If the specified operation (intent) does not map to a known URL endpoint, the node will throw an error indicating the operation is invalid. Verify the operation name matches one of the supported ScaleFluidly operations.
  • API connectivity issues: Network errors or incorrect environment URLs can cause failures. Confirm the selected environment URL is reachable and correct.
  • Invalid request body: Since the request body is user-provided JSON, malformed or incomplete JSON may cause API 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