ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to configuration, quoting, pricing, administration, and more. Specifically, for the Configure resource and the Remove User Favourite Product operation, it allows users to remove a product from a user's list of favorite products within the ScaleFluidly system.

Common scenarios where this node is beneficial include managing user preferences in sales or product management platforms, cleaning up outdated or incorrect favorite product entries, and automating user-specific product configurations.

For example, a sales automation workflow might use this node to dynamically update a user's favorite products based on recent purchases or changes in product availability.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development server), QA (quality assurance server), Local (local server). Determines the base URL for the API requests.
Request JSON object containing the request body specific to the operation. For "Remove User Favourite Product", this would include details identifying which user and product to remove from favorites.

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 respective request made to remove a user’s favorite product.

If the API returns binary data (not typical for this operation), it would be included accordingly, but primarily the output is structured JSON reflecting success, failure, or error messages from the API.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • May require an API authentication token (bearer token) provided via HTTP headers; this token must be available in the input data's headers.authorization field or configured through n8n credentials.
  • No other external dependencies are indicated.

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 input data includes valid authorization headers or configure the API credentials properly.
  • Operation not found: If the specified operation does not match any known intent URL mapping, an error will be thrown. Verify that the operation name is correct and supported.
  • API errors: Any errors returned by the ScaleFluidly API (e.g., invalid request body, unauthorized access) will be passed through in the output JSON. Check the request payload and authentication details if errors occur.
  • Environment URL issues: Selecting an incorrect environment may lead to connection failures. Confirm the environment setting matches the intended API server.

Links and References


Note: This summary is based solely on static analysis of the provided source code and property definitions.

Discussion