ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, pricing, configuration, and more. Specifically, for the Quote resource and the Get Quote Layout By Type operation, it retrieves the layout details of a quote based on its type from the selected environment.

Common scenarios where this node is useful include:

  • Automating retrieval of quote layouts to dynamically build user interfaces or forms.
  • Integrating quote data structures into workflows for further processing or validation.
  • Fetching quote metadata to customize sales or quoting applications.

For example, a sales automation workflow could use this node to fetch the layout of a specific quote type in the QA environment, then use that layout information to generate a custom quote form for users.

Properties

Name Meaning
Environment The target environment URL to send requests to. Options: Dev, QA, Local (with respective URLs).

Note: For this operation, the only input property required is the Environment, which determines the base URL for the API request.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested quote layout. Each item in the output corresponds to the layout data retrieved for the specified quote type.

The exact structure depends on the API response but generally includes fields describing the layout configuration, such as sections, fields, and their properties.

No binary data output is produced by this operation.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the chosen environment.
  • Optionally uses an authorization bearer token passed via the input data headers for authenticated requests.
  • No explicit credential configuration is mandatory, but if authentication is needed, an API key or token should be provided in the input data headers under authorization.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no token has been previously stored, the node will throw an error. Ensure the input data includes valid authorization headers.
  • Operation not found: If the operation name does not map to a known API endpoint, an error will be thrown. Verify the operation parameter is correctly set to "get_quote_layout_by_type" or the intended operation.
  • Request failures: Network issues or incorrect environment URLs can cause request errors. Confirm the environment URL is reachable and correct.
  • Invalid request body: If the request_info JSON parameter is malformed or missing required fields, the API may reject the request. Validate the JSON structure before execution.

Links and References


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

Discussion