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 administration within the ScaleFluidly platform. Specifically for the Quote resource and the Get QuoteVersions operation, it retrieves different versions of a quote from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

  • Retrieving historical or current versions of a sales quote to track changes over time.
  • Auditing quote modifications for compliance or review purposes.
  • Integrating quote version data into workflows for further processing or reporting.

For example, a sales automation workflow might use this node to fetch all versions of a quote before sending it for approval or generating a customer-facing document.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server).
Request JSON object containing the request body parameters specific to the operation. For "Get QuoteVersions", this would typically include identifiers or filters needed by the API to retrieve quote versions.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the Get QuoteVersions operation, the output JSON contains details about each version of the quote retrieved, such as version numbers, timestamps, status, and any other metadata provided by the API.

If the API returns binary data (not typical for this operation), it would be included in the binary output field, but this operation primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • An authorization token (Bearer token) must be present in the input data headers for authentication.
  • Optionally supports using an n8n credential for the ScaleFluidly API if no explicit token is provided.
  • No additional external dependencies beyond standard HTTP requests.

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 the input includes valid authorization or configure the API credentials properly.
  • Operation not found: If the specified operation or intent does not match any known mapping, the node throws an error indicating the operation is not found. Verify the operation name is correct and supported.
  • API errors: Any HTTP errors returned by the ScaleFluidly API (e.g., 401 Unauthorized, 404 Not Found) will propagate as node errors. Check the API token validity, endpoint URL, and request payload correctness.
  • Invalid JSON in Request property: The Request property must be valid JSON. Malformed JSON will cause the node to fail.

Links and References


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

Discussion