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 administrative tasks. Specifically for the Quote resource and the Get Account Layout operation, it retrieves the layout details of an account associated with a quote. This can be useful in scenarios where you need to dynamically fetch and display account layout information within your workflow, such as customizing UI forms or automating data processing based on account structure.

Practical examples include:

  • Fetching account layout metadata to build custom quote forms.
  • Automating validation or transformation of quote data based on account layout.
  • Integrating account layout info into reporting or dashboards.

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 Account Layout" operation. This is required and must conform to the API's expected input format 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 Account Layout" operation, the json output contains the account layout details retrieved from the API, which typically includes layout fields, sections, and metadata describing how the account data is structured.

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

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment (Dev, QA, or Local).
  • May require an API authentication token (Bearer token) passed via HTTP headers; this token is extracted from the first input item's JSON headers.authorization field or managed internally by n8n credentials if configured.
  • No other external dependencies are indicated.

Troubleshooting

  • Bearer token not found error: If the authorization header with a Bearer token is missing in the first input item, the node will throw an error. Ensure that the first input JSON includes a valid headers.authorization field with a Bearer token or configure the API credentials properly.
  • Operation not found error: If the specified operation does not exist in the internal intent-to-URL mapping, the node will throw an error. Verify that the operation name is correct and supported.
  • Invalid request body: Since the request body is user-provided JSON, malformed or incorrect request data may cause API errors. Validate the JSON structure against the API documentation.
  • Environment URL issues: Selecting an incorrect or unreachable environment URL will cause request failures. Confirm network connectivity and correct environment selection.

Links and References


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

Discussion