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 Category Discounts operation, it enables deletion of category discount entries within the ScaleFluidly system.

Common scenarios where this node is beneficial include automating administrative tasks related to pricing categories, managing discounts programmatically, and integrating these actions into broader workflows that require dynamic updates to category discounts.

For example, a user might use this node to automatically remove outdated or incorrect category discounts from their pricing database as part of a nightly cleanup process or in response to changes in business rules.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server). Determines the base URL used for requests.
Request JSON object containing the request body specific to the operation. For deleting category discounts, this would include identifiers or parameters required by the API to specify which discounts 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 result of the delete operation on category discounts, typically including status information or confirmation of deletion.

If the API returns binary data (not indicated here), it would be included accordingly, but based on the static analysis, output is JSON only.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • May require an API authentication token passed via an authorization header. This token is expected to be provided in the input data's headers or managed through n8n credentials configured for the ScaleFluidly API.
  • No explicit external libraries beyond standard n8n workflow helpers are needed.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization token in its headers, and no token has been previously stored in the node’s static data, the node will throw an error. Ensure that the input includes a valid bearer token or that the node is properly authenticated.
  • Operation not found: If the specified operation (intent) does not match any known operation in the internal intent-to-URL mapping, the node will raise an error indicating the operation is not found. Verify the operation name is correct and supported.
  • API errors: Any HTTP errors returned by the ScaleFluidly API will propagate as node errors. Check the request body format and API permissions if errors occur.

Links and References


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

Discussion