ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations grouped by resources such as Admin, Quote, Configure, Pricing, and MCP. Specifically for the Admin resource and the Get Currency Conversions operation, the node fetches currency conversion data from the ScaleFluidly service.

Typical use cases include:

  • Retrieving up-to-date currency conversion rates for financial or pricing calculations.
  • Integrating currency conversion data into workflows that require multi-currency support.
  • Automating administrative tasks related to currency management within the ScaleFluidly platform.

For example, a user might configure this node to pull current currency conversion rates from the ScaleFluidly API in their QA environment to update pricing models dynamically.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local (localhost).

The node also requires selecting the Resource (Admin) and Operation (Get Currency Conversions), but these are fixed based on your request.

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 call, which for "Get Currency Conversions" would typically include currency codes, conversion rates, timestamps, and possibly metadata about the conversions.
  • No binary data output is indicated or handled by this node.

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.
  • If no explicit authorization header is found in the first input item, the node attempts to use configured credentials named generically as an API key credential.
  • No other external dependencies or environment variables are explicitly required.

Troubleshooting

  • Bearer token not found error: This occurs if the first input item does not contain an authorization token in its headers and no API credential is configured. To fix, ensure the input includes a valid bearer token or configure the node with appropriate API credentials.
  • Operation not found error: If the specified operation (intent) is not recognized, verify that the operation name matches one of the supported operations for the Admin resource.
  • API request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request errors. Confirm the environment URL is correct and the token is valid.
  • Empty or malformed response: Ensure the API endpoint is reachable and the request body (if any) is correctly formatted JSON.

Links and References


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

Discussion