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, pricing, configuration, and administration. Specifically, for the Pricing resource and the Get QuoteLineItem Adjustment Values operation, the node fetches adjustment values related to quote line items from the ScaleFluidly service.

Typical use cases include:

  • Retrieving detailed pricing adjustments applied to individual quote line items.
  • Integrating pricing adjustments into sales or quoting workflows.
  • Automating price validation or auditing processes by fetching adjustment data programmatically.

For example, a sales automation workflow could use this node to pull adjustment values for quote line items to display accurate pricing breakdowns to customers or internal teams.

Properties

Name Meaning
Environment The target environment of the ScaleFluidly API. Options are:
- Dev (https://documentation-dev.scalefluidly.com)
- QA (https://documentation.scalefluidly.com)
- Local (http://localhost:8400)
Request JSON object representing the request body sent to the API endpoint. This contains the necessary parameters for the selected operation, e.g., identifiers for quote line items whose adjustment values are being requested.

Output

The node outputs an array of JSON objects under the json output field. Each object corresponds to the response from the ScaleFluidly API for the requested operation. For the "Get QuoteLineItem Adjustment Values" operation, the output JSON typically includes:

  • Adjustment details for each quote line item queried.
  • Pricing modifications, discounts, or other adjustment metadata as returned by the API.

No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoints corresponding to the chosen environment.
  • Optionally uses an API authentication token if provided in the input data headers; otherwise, it attempts to use configured credentials within n8n.
  • No explicit external libraries beyond standard HTTP request helpers 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 credential is configured, the node will throw an error. Ensure that either the input data includes a valid authorization token or that the node is configured with appropriate API credentials.
  • Operation not found: If the specified operation name does not map to a known API endpoint, the node throws an error indicating the operation was not found. Verify the operation parameter matches one of the supported operations.
  • API connectivity issues: Network errors or incorrect environment URLs can cause request failures. Confirm the environment URL is correct and accessible.
  • Invalid request body: The JSON request body must conform to the API's expected schema. Malformed or incomplete JSON may result in API errors.

Links and References


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

Discussion