ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as Admin, Quote, Configure, Pricing, and MCP. Specifically for the Admin resource and the Update Currency Conversion operation, it enables updating currency conversion data by sending a JSON request body to the appropriate ScaleFluidly API endpoint.

Common scenarios where this node is beneficial include automating administrative tasks related to currency conversions within an organization's financial or sales systems, ensuring up-to-date exchange rates or conversion rules are applied programmatically without manual intervention.

For example, a user might use this node to update currency conversion rates daily based on external data feeds or internal business logic, helping maintain accurate pricing and reporting in multi-currency environments.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server). Determines the base URL of the ScaleFluidly API.
Request The JSON-formatted request body containing the details needed to update the currency conversion. This must be provided according to the API's expected schema for the update operation.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each JSON object corresponds to the API response for the update currency conversion request, typically including status information, updated currency conversion details, or error messages if the update failed.

No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • An API authentication token (Bearer token) must be provided via the input data headers or configured credentials to authorize requests.
  • The node uses HTTP requests to communicate with the ScaleFluidly API; thus, network connectivity to the specified environment URLs is necessary.

Troubleshooting

  • Bearer token not found: If the authorization header with a Bearer token is missing in the first input item's JSON headers, the node will throw an error. Ensure that the token is correctly set in the input data or credentials.
  • Operation not found: If the specified operation does not match any known intent URL mapping, an error will occur. Verify that the operation name is correct and supported.
  • API request failures: Network issues, invalid JSON in the request body, or incorrect environment URLs can cause request failures. Check the environment setting, validate the JSON structure, and ensure the API token is valid.
  • Invalid JSON in Request property: Since the request body is passed as JSON, malformed JSON will cause errors. Use proper JSON formatting.

Links and References


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

Discussion