ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, orders, accounts, products, pricing, and administrative tasks. Specifically, for the Quote resource and the Get Complete Order Details operation, it retrieves comprehensive details about an order associated with a quote.

Common scenarios where this node is beneficial include:

  • Fetching detailed order information for processing or review within automated workflows.
  • Integrating order data into CRM or ERP systems.
  • Automating reporting or notifications based on complete order details.

For example, a sales automation workflow might use this node to pull all relevant order details after a quote is accepted, enabling downstream processes like invoicing or fulfillment.

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). Determines which ScaleFluidly API endpoint to use.
Request JSON object containing the request body parameters required by the API for the selected operation. This must be provided and formatted according to the API's expectations for "Get Complete Order Details".

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the Get Complete Order Details operation, the output JSON contains detailed information about the order linked to the quote, such as order items, pricing, status, customer details, and other metadata as returned 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 endpoints corresponding to the chosen environment.
  • Optionally uses an API authentication token passed via the authorization header in the input data; if not present, it attempts to use configured credentials named generically as an API key credential.
  • No additional external dependencies beyond standard HTTP request capabilities provided by n8n.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization token in its headers, and no credential is configured, the node will throw an error. Ensure that either the input includes a valid bearer token or the node is configured with appropriate API credentials.
  • Operation not found: If the specified operation (intent) does not match any known API endpoint mapping, the node throws an error indicating the operation is invalid. Verify the operation name is correct and supported.
  • Invalid request body: The request_info JSON must conform to the API's expected schema. Malformed or incomplete JSON may cause API errors.
  • Environment URL issues: Selecting an incorrect environment or having network connectivity problems to the chosen API base URL can cause request failures.

Links and References


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

Discussion