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 more. Specifically for the Quote resource and the Order Details operation, it retrieves detailed information about an order associated with a quote. This can be useful in sales automation workflows where you need to fetch comprehensive order data for processing, reporting, or further automation steps.

Practical examples include:

  • Automatically retrieving order details after a quote is approved to trigger fulfillment processes.
  • Fetching order information to update CRM records or generate invoices.
  • Integrating order data into dashboards or analytics tools for sales performance tracking.

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.

The Request property expects a JSON input that varies depending on the operation. For "get_order_details" under the Quote resource, this would typically include identifiers or filters needed by the API to locate the specific order details.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Order Details" operation, the output JSON contains detailed information about the order linked to the quote, such as order items, quantities, prices, statuses, and other relevant metadata.

If the API returns binary data (not typical for this operation), it would be included accordingly, but based on the static code analysis, the output is primarily JSON.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token if provided via credentials or headers.
  • No explicit external libraries beyond standard n8n helpers and HTTP request utilities are required.

Troubleshooting

  • Bearer token not found: If the authorization header is missing in the first input item, the node throws an error. Ensure that the API key or token is correctly set either in the node credentials or passed in the input data headers.
  • Operation not found: If the specified operation does not match any known intent URL mapping, the node will throw an error indicating the operation is invalid. Verify the operation name is correct and supported.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies may cause the API call to fail. Check the environment setting, request JSON structure, and API credentials.
  • Malformed JSON in Request: Since the request body is user-provided JSON, ensure it is well-formed and matches the expected schema for the operation.

Links and References


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

Discussion