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 Get Product Categories operation, it allows users to retrieve product category data from the ScaleFluidly system.

Typical use cases include:

  • Fetching product categories to display or process them in workflows.
  • Integrating product category data into sales, inventory, or catalog management automations.
  • Using retrieved categories as inputs for further API calls or decision-making steps within n8n workflows.

For example, a user might automate the synchronization of product categories between ScaleFluidly and another system or generate reports based on category data.

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 ScaleFluidly instance the node interacts with.
Request JSON object representing the request body sent to the API. Required for this operation.

The Request property is a free-form JSON input where you specify any parameters or filters needed by the "Get Product Categories" API endpoint.

Output

The node outputs an array of JSON objects corresponding to the API response(s) from ScaleFluidly. Each item in the output array contains the parsed JSON data returned by the "Get Product Categories" endpoint.

  • The json field holds the structured data about product categories.
  • No binary data output is indicated for this operation.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • Optionally uses an API authentication token passed via HTTP headers (Bearer token). The node expects this token to be provided in the input data's headers.authorization field on the first item or managed via n8n credentials if configured.
  • No other external dependencies are required.

Troubleshooting

  • Bearer token not found error: 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 token is correctly set in the input or configure the API credentials properly.
  • Operation not found error: If the operation name does not map to a known API endpoint, the node will report an error. Verify that the operation name is correct and supported.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause request errors. Check the environment URL, request JSON format, and API permissions.
  • Empty or malformed response: Confirm that the request body matches the expected schema for the "Get Product Categories" API and that the API service is operational.

Links and References

Note: Replace these URLs with your actual API documentation links if different.

Discussion