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 Get Shared Templates operation, it retrieves shared quote templates from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

  • Automating retrieval of shared quote templates for use in sales or quoting workflows.
  • Integrating ScaleFluidly quote data into other systems or processes within an automation workflow.
  • Fetching templates dynamically based on environment (Dev, QA, Local) for testing or production use.

Example: A sales team could use this node to automatically fetch the latest shared quote templates before generating a new quote, ensuring consistency and up-to-date information.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local
Request JSON object containing the request body parameters specific to the "Get Shared Templates" operation. This typically includes any filters or parameters required by the API endpoint.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Shared Templates" operation, the output JSON contains details about the shared quote templates retrieved, such as template IDs, names, descriptions, and other metadata as provided by the API.

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

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token passed via the authorization header. This token must be available in the input data headers or configured through n8n credentials.
  • No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

  • Bearer token not found: If the authorization token is missing from the first input item’s headers and not stored in static workflow data, the node will throw an error. Ensure that the input data includes a valid bearer token in the authorization header or configure the API credentials properly.
  • Operation not found: If the specified operation or intent does not match any known mapping, an error will occur. Verify that the operation name is correct and supported.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause request errors. Check the environment selection and the JSON structure of the request body.
  • Invalid JSON in Request property: The Request property must contain valid JSON. Malformed JSON will cause parsing errors.

Links and References


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

Discussion