ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations related to quotes, orders, pricing, configuration, and administrative tasks within the ScaleFluidly platform. Specifically, for the Quote resource and the Get Layout for Order operation, it retrieves the layout details associated with an order, which can be useful for dynamically generating or displaying order forms or interfaces based on the current order structure.

Common scenarios where this node is beneficial include:

  • Automating retrieval of order layouts to customize user interfaces in sales or quoting applications.
  • Integrating ScaleFluidly order data into other systems or workflows that require knowledge of the order's layout.
  • Dynamically adjusting UI components or validations based on the retrieved layout information.

Example: A sales automation workflow could use this node to fetch the layout of a customer's order to display relevant fields and sections in a custom CRM interface.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local (localhost).

The node also requires selecting the Resource (quote) and Operation (get_layout_for_order), but these are fixed by your selection.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Layout for Order" operation, the output JSON typically contains the layout structure details of the specified order, such as field groups, field metadata, visibility rules, and ordering information.

If the API returns binary data (not indicated here), it would represent files or attachments related to the layout, but this node primarily deals with JSON responses describing layouts.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • May require an API authentication token (Bearer token) provided via HTTP headers in the input data or configured credentials.
  • No explicit internal credential names are exposed; users must supply valid authorization tokens.
  • The node uses standard HTTP requests with JSON payloads.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no prior token was stored, the node will throw an error. Ensure the input includes a valid authorization token or configure credentials properly.
  • Operation not found error: If the operation name does not map to a known intent URL, the node throws an error. Verify the operation name matches one of the supported operations.
  • API request failures: Network issues, invalid tokens, or incorrect environment URLs may cause request errors. Check connectivity, token validity, and environment selection.
  • Malformed request body: The request_info parameter must be valid JSON matching the expected API schema for the operation.

Links and References


If you need further details about other operations or resources, please provide their names.

Discussion