ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

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 Save Product Group Options operation, the node sends a JSON request body to the ScaleFluidly API endpoint responsible for saving or updating product group options.

Typical use cases include automating the management of product group options within an organization's product catalog or pricing system. For example, a user might update configuration options for product groups in bulk or programmatically adjust product attributes tied to specific groups.

Properties

Name Meaning
Environment The target environment 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 The JSON-formatted request body containing the data to save or update product group options. This is required and must conform to the API's expected schema for this operation.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each response corresponds to the result of the "save product group options" API call, typically including confirmation of success, updated product group option details, or error information if the request failed.

No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token (bearer token) passed via HTTP headers for authorization.
  • The node supports using either direct bearer tokens provided in input data or credentials configured in n8n under a generic API key credential.
  • Proper network connectivity to the selected environment URL is necessary.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token and no global authorization header has been set, the node will throw an error. Ensure that the authorization token is correctly provided either in the input data or via node credentials.
  • Operation not found: If the specified operation or intent name does not match any known API endpoint mapping, the node will raise an error indicating the operation was not found. Verify the operation name matches exactly one of the supported operations.
  • Invalid JSON request body: Since the request body is user-provided JSON, malformed or incorrect data structures may cause API errors. Validate the JSON structure against the ScaleFluidly API documentation before execution.
  • Network or environment issues: Selecting an incorrect environment URL or having network restrictions can lead to connection failures. Confirm the environment setting and network accessibility.

Links and References

  • ScaleFluidly API Documentation (QA environment)
  • Refer to the ScaleFluidly API docs for detailed schemas and examples of the "save product group options" request body and response format.

Discussion