ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, configuration, pricing, and administrative tasks. Specifically for the Quote resource and the Create Quote Version operation, it allows users to create a new version of an existing quote by sending a structured JSON request to the ScaleFluidly backend.

Common scenarios where this node is beneficial include:

  • Automating quote versioning workflows in sales or finance processes.
  • Integrating quote management into larger automation pipelines.
  • Creating updated versions of quotes programmatically based on changing customer requirements or pricing adjustments.

For example, a sales team could use this node to automatically generate a new quote version whenever a customer requests changes, ensuring all versions are tracked and managed consistently.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server).
Request The JSON body of the request containing details required to create the quote version. This must be a valid JSON object matching the API's expected schema for creating a quote version.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each JSON object corresponds to the API response for the "Create Quote Version" operation, typically including details about the newly created quote version such as its ID, status, timestamps, and any other metadata returned by the API.

If the API supports binary data output, it would be handled accordingly, but based on the static analysis, this node primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token (Bearer token) passed via the authorization header in the input data or through configured credentials.
  • No explicit external libraries beyond standard n8n workflow helpers and HTTP request utilities are needed.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization token in its headers, and no prior token was stored, the node will throw an error. Ensure that the input data includes a valid Bearer token in the authorization header or configure the node with appropriate credentials.
  • Operation not found error: If the specified operation or intent does not match any known URL mapping, the node will fail. Verify that the operation name is correct and supported.
  • Invalid JSON in Request property: The Request field must contain valid JSON. Malformed JSON will cause the API call to fail.
  • API connectivity issues: Check network access to the selected environment URL and ensure the API service is reachable.

Links and References


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

Discussion