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 Predefined Grouping operation, the node sends a JSON request body to the ScaleFluidly API endpoint corresponding to predefined grouping functionality.

Typical use cases include automating product grouping configurations within a sales or quoting system, managing how products are grouped based on predefined rules, and streamlining quote or product setup processes. For example, a sales automation workflow could use this node to apply predefined groupings to products in a quote before sending it to a customer.

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 API instance the node will communicate with.
Request A JSON object representing the request body sent to the ScaleFluidly API for the selected operation. It must be provided and formatted according to the API's expectations for the "predefined_grouping" operation under the Configure resource.

Output

The node outputs an array of JSON objects, each representing the response from the ScaleFluidly API for each input item processed. The json output field contains the parsed JSON response from the API call.

If the API returns binary data, it would be included accordingly, but based on the static analysis and typical usage, the output is primarily JSON data reflecting the result of the predefined grouping operation.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if provided in the input data headers or via configured credentials.
  • The node expects an authorization bearer token either passed in the first input item's JSON headers or managed through n8n credentials.
  • No other external dependencies are required beyond standard HTTP request capabilities.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no credential-based authentication is configured, the node will throw an error. Ensure that the authorization token is correctly set in the input or credentials.
  • Operation not found error: If the specified operation (intent) does not match any known mapping, the node will throw an error indicating the operation was not found. Verify that the operation name is correct and supported.
  • Invalid JSON in Request property: The request_info property must be valid JSON matching the API's expected schema. Malformed JSON or missing required fields may cause API errors.
  • Environment URL issues: Selecting an incorrect environment or having network connectivity issues to the chosen API base URL can cause request failures.

Links and References


This summary focuses on the Configure resource with the Predefined Grouping operation, describing how the node constructs and sends requests to the ScaleFluidly API and handles responses accordingly.

Discussion