ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to configuration, quotes, pricing, administration, and more. Specifically for the Configure resource and the Create Favorite Cart operation, it allows users to send a custom JSON request body to create a favorite cart configuration in the ScaleFluidly system.

Common scenarios where this node is beneficial include automating the management of product configurations, saving user-preferred carts for quick reuse, and integrating ScaleFluidly's configuration capabilities into broader workflows such as sales automation or product lifecycle management.

For example, a sales team could use this node to programmatically save a customer's preferred product bundle as a favorite cart, enabling faster quote generation later.

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). Selects which ScaleFluidly instance to interact with.
Request A JSON object representing the request body sent to the ScaleFluidly API for creating the favorite cart. This should contain all necessary data fields as required by the API endpoint for favorite cart creation.

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed. Each JSON object contains the API response data for the create favorite cart operation, typically including confirmation details, identifiers, or error messages returned by the API.

If the API supports binary data in responses, the node would handle it accordingly, but based on the provided code and properties, the output is primarily JSON structured data.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Needs an API authentication token (bearer token) passed via HTTP headers; this token must be available in the input data's headers.authorization field or managed through n8n credentials configured for the ScaleFluidly API.
  • The node uses the selected environment URL to direct requests.
  • No other external dependencies are indicated.

Troubleshooting

  • Bearer token not found: If the authorization token is missing from the first input item's headers and not stored in static workflow data, the node will throw an error. Ensure that the input JSON includes a valid bearer token in headers.authorization.
  • Operation not found: If the specified operation or intent does not match any known API endpoint mapping, the node throws an error indicating the operation is not found. Verify the operation name and ensure it is supported.
  • Invalid JSON in Request: The request_info property expects valid JSON. Malformed JSON will cause request failures.
  • API Errors: Any errors returned by the ScaleFluidly API (e.g., invalid parameters, authentication failure) will be included in the node output. Review these messages to adjust the request payload or authentication.

Links and References


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

Discussion