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 QuoteDataLanding Page operation, it fetches detailed quote data from the ScaleFluidly system. This is useful in scenarios where you want to retrieve up-to-date quote information programmatically within an n8n workflow, such as automating sales processes, generating reports, or syncing quote data with other systems.

For example, a sales automation workflow could use this node to pull quote details when a new quote is created or updated, then trigger follow-up actions like notifications or CRM updates.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options:
- Dev (development)
- QA (quality assurance)
- Local (local server)

The node also requires selecting the Resource as "Quote" and the Operation as "Get QuoteDataLanding Page" (implied by your selection). Additionally, it accepts a JSON input property named request_info which contains the request body sent to the API endpoint.

Output

The node outputs an array of JSON objects under the json field. Each object corresponds to the response from the ScaleFluidly API for the requested quote data. The structure depends on the API's response schema but generally includes detailed quote information such as line items, pricing, participants, statuses, and metadata relevant to the quote.

No binary data output is indicated or handled by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token passed via HTTP headers (authorization header).
  • The node can work with an API key credential configured in n8n or accept bearer tokens dynamically from input data.
  • No additional external libraries beyond standard n8n helpers are used.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no static token is stored, the node will throw an error. Ensure that the input data includes valid authorization headers or configure credentials properly.
  • Operation not found error: If the specified operation (intent) does not match any known mapping, the node throws an error indicating the operation is invalid. Verify the operation name matches one of the supported intents.
  • Request failures: Network issues, incorrect environment URLs, or invalid request bodies may cause API call failures. Check the environment setting and ensure the request_info JSON is correctly structured per API requirements.

Links and References


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

Discussion