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 Delete Currency Conversion operation, the node sends a request to delete a currency conversion entry in the ScaleFluidly system.

Common scenarios where this node is beneficial include automating administrative tasks related to currency conversions within an organization's financial or pricing systems. For example, if a currency conversion rate becomes obsolete or incorrect, this node can be used to programmatically remove it from the system, ensuring that pricing calculations remain accurate.

Practical example:

  • An admin wants to clean up outdated currency conversion rates after a major currency revaluation.
  • Automating deletion of currency conversions as part of a scheduled maintenance workflow.

Properties

Name Meaning
Environment The target environment URL for the API call. Options: Dev, QA, Local
Request JSON object containing the request body details required by the Delete Currency Conversion API endpoint

The Environment property selects which ScaleFluidly API environment to target (development, quality assurance, or local). The Request property must contain the necessary JSON payload for the delete currency conversion operation, typically including identifiers or parameters specifying which currency conversion to delete.

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 delete currency conversion request.

If the API returns binary data (not indicated here), it would represent associated files or attachments related to the operation, but this node primarily deals with JSON responses.

Dependencies

  • Requires access to the ScaleFluidly API endpoints specified by the selected environment.
  • May require an API authentication token (Bearer token) provided via HTTP headers in the input data or configured credentials.
  • No explicit internal credential names are exposed; users must provide valid authorization tokens as part of the input or node configuration.

Troubleshooting

  • Bearer token not found error: The node expects an authorization header with a Bearer token in the first input item's JSON under headers.authorization. If missing, the node will throw an error. Ensure the token is correctly passed in the input or configured in the node's credentials.
  • Operation not found error: If the operation name does not match any known intent URL mapping, the node throws an error indicating the operation is invalid. Verify the operation name is correct and supported.
  • API request failures: Network issues, invalid request bodies, or insufficient permissions may cause API errors. Check the request JSON structure and ensure the API token has appropriate rights.
  • Empty or malformed request body: The request_info JSON must be well-formed and include all required fields for the delete currency conversion API call.

Links and References


This summary focuses on the Admin resource's Delete Currency Conversion operation based on the provided properties and source code analysis.

Discussion