ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations related to quotes, configuration, pricing, and more within the ScaleFluidly platform. Specifically, for the Quote resource and the Get Templates List operation, it fetches a list of quote templates from the selected environment.

Common scenarios where this node is beneficial include:

  • Automating retrieval of available quote templates to dynamically populate UI elements or workflows.
  • Integrating quote template data into other systems or processes without manual intervention.
  • Streamlining quote creation by selecting from predefined templates fetched via this node.

Example use case: A sales automation workflow that retrieves all quote templates from the QA environment to present options to sales reps before generating a new quote.

Properties

Name Meaning
Environment The target ScaleFluidly API environment to connect to. Options: Dev, QA, Local.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Templates List" operation under the Quote resource, the output JSON contains the list of quote templates retrieved from the API.

The exact structure depends on the API response but typically includes fields describing each template such as template ID, name, description, and other metadata relevant to quote templates.

No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the chosen environment (Dev, QA, or Local).
  • If authentication is needed, the node expects a bearer token in the input data's headers or uses an API key credential configured in n8n.
  • No additional external dependencies beyond standard HTTP request capabilities.

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 stored authorization header exists. Ensure the input data includes valid authorization or configure credentials properly.
  • Operation not found error: If the specified operation (intent) does not match any known mappings, verify the operation name is correct and supported.
  • API connectivity issues: Check network access to the selected environment URL and ensure the API service is reachable.
  • Invalid request body: For operations requiring a JSON request body, ensure the provided JSON is well-formed and matches expected API schema.

Links and References


Note: This summary is based solely on static analysis of the provided source code and property definitions. Runtime behavior may vary depending on actual API responses and configurations.

Discussion