ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as quotes, configuration, pricing, admin, and MCP (a custom action). Specifically for the Configure resource and the Delete Bundle operation, the node sends a request to delete a product bundle configuration in the ScaleFluidly system.

Typical use cases include automating the management of product bundles within a sales or pricing platform, such as removing outdated or incorrect bundles from the configuration. This can be part of workflows that maintain product catalogs or update pricing structures dynamically.

For example, a user might trigger this node to delete a specific product bundle after a promotion ends or when a bundle is no longer offered.

Properties

Name Meaning
Environment The target environment for the API call. Options are:
- Dev: Development environment URL
- QA: Quality Assurance environment URL
- Local: Localhost URL for testing
Request JSON object containing the request body details required by the API to perform the delete bundle operation. This typically includes identifiers or parameters specifying which bundle 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 bundle request, typically indicating success or failure of the deletion.

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

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; otherwise, it attempts to use configured credentials.
  • No explicit external libraries beyond n8n's standard HTTP request helpers are needed.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token and no credential is configured, the node will throw an error. Ensure that either the API key/authorization token is set in the node credentials or passed in the input data headers.
  • Operation not found: If the specified operation or intent does not match any known API endpoint mapping, the node throws an error indicating the operation is invalid. Verify the operation name is correct.
  • API request failures: Network issues, incorrect environment URLs, or malformed request bodies may cause API errors. Check the request JSON structure and environment selection.
  • Empty or invalid request body: The request_info property must be a valid JSON object matching the API's expected schema for deleting bundles.

Links and References


This summary focuses on the Configure resource's Delete Bundle operation as requested, based on static code analysis of the bundled source and provided properties.

Discussion