ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to different resources such as quotes, pricing, configuration, and more. Specifically, for the Quote resource with the Get Quote Types operation, it retrieves the types of quotes available in the ScaleFluidly system.

Common scenarios where this node is beneficial include:

  • Automating workflows that require fetching quote metadata or types before creating or managing quotes.
  • Integrating ScaleFluidly quote data into other systems or dashboards.
  • Dynamically populating UI elements or decision logic based on available quote types.

For example, a sales automation workflow might use this node to fetch all quote types to present options to a user or to validate incoming quote data against supported types.

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_quote_types), but since you specified only the "Environment" property explicitly, this is the main configurable input for this operation.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the Get Quote Types operation, the output JSON typically contains details about each quote type, such as identifiers, names, descriptions, or other metadata fields defined by the API.

The output structure is:

[
  {
    "id": "string",
    "name": "string",
    "description": "string",
    ...
  },
  ...
]

(Note: Exact fields depend on the ScaleFluidly API response schema.)

No binary data output is involved in this operation.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • May require an API authentication token (bearer token) passed via HTTP headers. This token is expected to be provided in the input data's headers.authorization field on the first item or managed via n8n credentials if configured.
  • No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

  • Bearer token not found error: If the authorization header with a bearer token is missing in the first input item's JSON headers, the node will throw an error. Ensure that the input data includes a valid authorization token or configure the node with appropriate credentials.
  • Operation not found error: If the operation name does not map to a known intent URL, the node throws an error indicating the operation is invalid. Verify that the operation parameter is correctly set to "get_quote_types".
  • API connectivity issues: Network errors or incorrect environment URLs can cause request failures. Confirm the environment URL is reachable and correct.
  • Invalid request body: Although this operation likely does not require a request body, providing malformed JSON in the request_info parameter may cause errors.

Links and References


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

Discussion