ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations related to quotes, accounts, pricing, configuration, and administration within the ScaleFluidly platform. Specifically, for the Quote resource and Get Accounts operation, it fetches account information from the ScaleFluidly system.

Typical use cases include:

  • Retrieving a list of accounts associated with quotes for reporting or processing.
  • Integrating account data into workflows that manage quotes or sales processes.
  • Automating data retrieval from different environments (Dev, QA, Local) for testing or production purposes.

For example, a user might configure this node to get all accounts linked to a particular quote in the QA environment to validate data before sending a proposal.

Properties

Name Meaning
Environment The target environment URL for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). This determines which backend instance the request is sent to.
Request JSON object containing the request body parameters specific to the "Get Accounts" operation. This allows passing filters, pagination, or other query details as required by the API.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. Each item in the output corresponds to one API response per input item processed.

  • The json field contains the parsed JSON response from the API, typically including account details such as account IDs, names, statuses, and other metadata depending on the API's response schema.
  • If the API returns binary data (not typical for "Get Accounts"), it would be included accordingly, but this operation primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token if provided in the input data headers under authorization.
  • No explicit internal credential type names are exposed; users must provide necessary authentication tokens or credentials configured in n8n.
  • The node depends on the n8n HTTP request helper methods to communicate with the ScaleFluidly API.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no prior token was stored, the node will throw an error. Ensure that the input data includes valid authorization headers or that credentials are properly configured.
  • Operation not found: 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 supported actions.
  • API connectivity issues: Network errors or incorrect environment URLs can cause request failures. Confirm the environment URL is correct and accessible.
  • Invalid JSON in Request property: The request_info property must be valid JSON. Malformed JSON will cause the node to fail.

Links and References


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

Discussion