ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various administrative and operational tasks related to product management, quoting, pricing, configuration, and more within the ScaleFluidly platform. Specifically, for the Admin resource and Add Product operation, it enables adding new products by sending a structured JSON request to the appropriate ScaleFluidly API endpoint.

Common scenarios where this node is beneficial include automating product catalog updates, integrating product data from external systems, or managing product-related workflows programmatically within n8n. For example, a user can automate adding new products to their inventory system whenever a new product is created in an external database or ERP system.

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)
Request The JSON-formatted request body containing the details of the product to add. This must conform to the expected API schema for adding a product.

Output

The node outputs an array of JSON objects corresponding to the responses received from the ScaleFluidly API for each input item processed. Each JSON object contains the API response data, which typically includes confirmation of the product addition, any generated IDs, status messages, or error information if the request failed.

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

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if configured; otherwise, it expects a bearer token in the input data headers.
  • No explicit internal credential names are exposed; users must provide valid authorization tokens either via node credentials or input data headers.
  • The node requires network connectivity to the selected environment URL.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token and no credential is set, the node will throw an error. Ensure that either the node credentials are configured with a valid API key/token or the input data includes the required authorization header.
  • Operation not found: If the specified operation (intent) does not match any known API endpoint mapping, the node will throw an error indicating the operation is not found. Verify the operation name is correct and supported.
  • Invalid JSON in Request: The Request property must be valid JSON matching the API's expected schema. Malformed JSON or missing required fields may cause API errors.
  • Network issues: Connectivity problems to the chosen environment URL will result in request failures. Confirm the environment URL is reachable and correct.

Links and References


This summary focuses on the Admin resource's Add Product operation as requested, based on static analysis of the provided source code and property definitions.

Discussion