ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

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 Discounts operation, it enables retrieval of discount information related to product categories managed within the ScaleFluidly platform.

Typical use cases include:

  • Fetching current category discount details to display or process in workflows.
  • Automating reporting or synchronization tasks involving category discounts.
  • Integrating category discount data into other systems or processes for pricing or promotional analysis.

For example, a sales automation workflow could use this node to pull category discount data dynamically before generating quotes or pricing proposals.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local (with respective URLs).
Request JSON object representing the request body payload sent to the API endpoint. Required for all operations including "Get Category Discounts".

The Request property is a flexible JSON input that allows specifying any parameters or filters required by the API for the selected operation. For "Get Category Discounts," this would typically include identifiers or query parameters relevant to fetching category discount data.

Output

The node outputs an array of JSON objects under the json field. Each object corresponds to the response from the ScaleFluidly API for the requested operation.

For the "Get Category Discounts" operation, the output JSON will contain details about category discounts such as discount rates, applicable categories, validity periods, and other metadata as provided by the API.

No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if configured; otherwise, it expects a bearer token passed via input data headers.
  • No explicit external npm packages beyond n8n's standard helpers are required.
  • The node requires proper configuration of the environment URL and valid authorization credentials to successfully communicate with the API.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no credential is configured, the node will throw an error. Ensure that either an API key credential is set up or the input includes a valid bearer token.
  • Operation not found: If the specified operation (intent) does not match any known API endpoint mapping, the node will raise an error indicating the operation is invalid. Verify the operation name matches one of the supported actions.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause HTTP errors. Check the environment selection and the JSON structure of the request body.
  • Empty or malformed request_info: Since the request body is user-defined JSON, ensure it conforms to the expected schema for the operation to avoid API errors.

Links and References

These links provide detailed API specifications and examples for constructing request bodies and understanding responses.

Discussion