ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations across multiple resources such as quotes, configuration, pricing, admin, and MCP. Specifically, for the Configure resource and the Delete Favorite Cart operation, it sends a request to delete a saved favorite cart configuration in the ScaleFluidly system.

Typical use cases include automating the management of user or system configurations related to favorite carts, such as removing obsolete or unwanted favorite cart entries programmatically within an n8n workflow. This can be useful in e-commerce or sales platforms where users maintain favorite product bundles or carts that need to be updated or cleaned up automatically.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). Determines which backend instance the request is sent to.
Request JSON object containing the request body specific to the "Delete Favorite Cart" operation. This should include all necessary parameters required by the API to identify and delete the favorite cart.

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 favorite cart request, typically indicating success or failure of the deletion operation.

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

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.
  • No explicit internal credential names are exposed; users must configure appropriate API authentication credentials in n8n if needed.
  • The node depends on the n8n HTTP request helper methods to send requests to the ScaleFluidly API.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no prior token was stored, the node will throw an error. Ensure that the input JSON includes a valid authorization token or that the node is configured with proper credentials.
  • Operation not found error: If the operation name does not map to a known intent URL, the node throws an error. Verify that the operation parameter is correctly set to "delete_favorite_cart" under the Configure resource.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies may cause API errors. Check the request JSON structure and environment selection.
  • Empty or malformed request body: The request_info property must be a valid JSON object matching the API's expected schema for deleting a favorite cart.

Links and References


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

Discussion