ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quote configuration, pricing, product management, and administrative tasks. Specifically, for the Configure resource and the Quote LineItems Summary operation, it sends a custom JSON request body to the ScaleFluidly API endpoint corresponding to this operation and returns the summarized data about quote line items.

Typical use cases include:

  • Retrieving summarized information about line items in a sales quote.
  • Automating quote configuration workflows by fetching detailed line item summaries.
  • Integrating quote data into other systems or dashboards for analysis or reporting.

For example, a sales automation workflow could use this node to fetch a summary of all products and their quantities in a quote before sending it for approval or generating a proposal document.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server).
Request A JSON object representing the request body sent to the API. This contains parameters specific to the "Quote LineItems Summary" operation.

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 Quote LineItems Summary operation, the output JSON typically includes summarized details of the quote's line items such as product identifiers, quantities, prices, discounts, and other relevant metadata.

No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if provided in the input data headers; otherwise, it attempts to use credentials configured in n8n under a generic API key credential.
  • The node requires proper network connectivity to the selected environment URL (Dev, QA, or Local).

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token and no API credentials are configured, the node will throw an error. Ensure that either the input data includes a valid authorization token or the node has appropriate API credentials set up.
  • Operation not found: If the specified operation (intent) does not match any known API endpoint mapping, the node will throw an error indicating the operation was not found. Verify the operation name is correct and supported.
  • API request failures: Network issues, invalid request bodies, or incorrect environment URLs can cause request failures. Check the environment setting and validate the JSON request body format.
  • Invalid JSON in Request property: Since the request body is user-provided JSON, malformed JSON will cause errors. Validate JSON syntax before running the node.

Links and References


If you need further details on other operations or resources, please provide additional context.

Discussion