ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to configuration, quotes, pricing, administration, and more. Specifically, for the Configure resource and the Get User Products By Filter operation, it allows users to retrieve a filtered list of products associated with a user based on criteria specified in the request body.

Common scenarios where this node is beneficial include:

  • Fetching product data tailored to specific user filters for dynamic catalog displays.
  • Integrating product filtering capabilities into workflows that automate sales or inventory processes.
  • Enabling customized product recommendations or selections based on user attributes or preferences.

For example, a sales automation workflow could use this node to get all products available to a particular user filtered by category or price range, then proceed to create quotes or orders based on those products.

Properties

Name Meaning
Environment The target environment URL for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). This determines which backend instance the node will communicate with.
Request JSON object representing the request body sent to the API. This contains filter criteria and other parameters required by the "Get User Products By Filter" operation. It must be provided and formatted according to the API's expectations.

Output

The node outputs an array of JSON objects under the json field. Each object corresponds to a response from the ScaleFluidly API for the requested operation. For the "Get User Products By Filter" operation, the output typically includes product details matching the filter criteria such as product IDs, names, categories, prices, availability, and any other metadata returned by the API.

No binary data output is indicated for this operation.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token (Bearer token) passed via HTTP headers if present in input data; otherwise, it attempts to use configured credentials named generically as an API key credential.
  • No explicit environment variables are required beyond what is configured in n8n for API authentication.

Troubleshooting

  • Missing Bearer Token Error: If the first input item does not contain an authorization header with a bearer token and no API credential is configured, the node throws an error "Bearer token not found". To resolve, ensure the input data includes proper authorization headers or configure the API authentication credential in n8n.
  • Operation Not Found: If the operation name does not map to a known API endpoint, the node throws an error indicating the operation was not found. Verify that the operation parameter is correctly set to "get_user_products_by_filter" for this use case.
  • Invalid Request Body: Since the request body is user-provided JSON, malformed or incomplete JSON may cause API errors. Validate the JSON structure before execution.
  • Environment URL Issues: Selecting an incorrect environment or having network issues connecting to the chosen environment URL can cause request failures. Confirm the environment setting matches your deployment.

Links and References

Discussion