ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, orders, products, pricing, configuration, and administration within the ScaleFluidly platform. Specifically, for the Quote resource and the Get Orders operation, it retrieves order data from the ScaleFluidly system.

Typical use cases include:

  • Fetching detailed order information linked to quotes for sales or finance teams.
  • Automating workflows that require up-to-date order status or details.
  • Integrating order data into other systems or dashboards for reporting or analysis.

For example, a user might configure this node to pull all orders associated with a particular quote to trigger downstream processing like invoicing or shipment scheduling.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local (with URLs).
Request JSON object containing the request body parameters specific to the "Get Orders" operation.
  • Environment selects which ScaleFluidly API endpoint to use.
  • Request is a JSON input where you specify filters or parameters required by the Get Orders API call.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the Get Orders operation, the output JSON typically contains order details such as order IDs, statuses, dates, line items, and other relevant metadata returned by the API.

No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoints specified by the selected environment.
  • Optionally uses an API authentication token (bearer token) passed in the HTTP headers for authorization.
  • If no explicit bearer token is found in the input data, the node attempts to use credentials configured in n8n under a generic API key credential.
  • No additional external dependencies beyond standard HTTP requests.

Troubleshooting

  • Bearer token not found error: This occurs if the first input item does not contain an authorization header with a bearer token and no API credentials are configured. To fix, ensure your workflow provides a valid bearer token or configure the API credentials in n8n.
  • Operation not found error: If the operation name (intent) does not match any known API endpoint mapping, the node will throw an error. Verify the operation name is correct and supported.
  • API request failures: Network issues, invalid request JSON, or incorrect environment URLs can cause request errors. Check the environment setting and the structure of the JSON request body.
  • Empty or malformed response: Ensure the request JSON matches the expected schema for the Get Orders API call.

Links and References


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

Discussion