ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API
Join our community

Actions224

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as Admin, Quote, Configure, Pricing, and MCP. Specifically, for the Admin resource and the Get Category Details operation, the node fetches detailed information about a specific category from the ScaleFluidly system.

Typical use cases include:

  • Retrieving metadata or configuration details about product categories in an administrative context.
  • Automating workflows that require up-to-date category information for reporting or decision-making.
  • Integrating category data into other systems or dashboards.

For example, a user might want to get detailed attributes of a product category to display on a sales dashboard or to validate category settings before processing orders.

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). Determines which backend environment the request is sent to.
Request JSON object containing the request body parameters required by the "Get Category Details" operation. This typically includes identifiers or filters needed by the API to return the correct category details.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Category Details" operation, the output JSON contains detailed information about the specified category, such as its attributes, associated products, pricing, discounts, or other metadata depending on the API's response structure.

If the API returns binary data (not typical for this operation), it would be included in the binary output field, but this operation primarily deals with JSON data.

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 named generically as an API key credential.
  • No explicit external libraries beyond standard n8n workflow helpers are required.
  • The node expects the user to provide valid JSON-formatted request bodies matching the API's expected schema for the operation.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token and no credentials are configured, the node will throw an error. Ensure that either the input data includes a valid authorization token or that the node is configured with appropriate API credentials.
  • Operation not found error: If the operation name (intent) does not match any known operation in the internal mapping, the node will fail. Verify that the operation name is correctly set to "get_category_details" for this use case.
  • Invalid JSON in Request property: The request_info property must be valid JSON. Malformed JSON will cause the node to fail.
  • Environment URL issues: Selecting an incorrect or unreachable environment URL will result in network errors. Confirm the environment setting matches the intended backend.

Links and References

Discussion