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 Update Price Book Associated Products operation, it enables updating the products associated with a price book in the ScaleFluidly system.

Common scenarios where this node is beneficial include automating product management within price books, synchronizing product data between systems, or programmatically adjusting pricing structures based on business logic. For example, a user might update the list of products linked to a specific price book after a product catalog change or promotional campaign.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options are:
- Dev (https://documentation-dev.scalefluidly.com)
- QA (https://documentation.scalefluidly.com)
- Local (http://localhost:8400)
Request JSON object representing the request body sent to the API for the selected operation. This contains all necessary data to update the price book associated products.

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed. Each JSON object represents the API response for the respective update operation performed on the price book's associated products.

If the API returns binary data (not indicated explicitly here), it would be included accordingly, but primarily the output is JSON structured data reflecting the result of the update operation.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • Optionally uses an API authentication token if provided via HTTP headers or credentials configured in n8n.
  • No explicit external libraries beyond standard n8n workflow helpers and request utilities are required.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no prior token is stored, the node will throw an error. Ensure that the authorization token is correctly passed in the input data or configured in credentials.
  • Operation not found error: If the specified operation (intent) does not match any known API endpoint mapping, the node will raise an error. Verify that the operation name is correct and supported.
  • API request failures: Network issues, invalid request bodies, or incorrect environment URLs can cause request failures. Check the environment setting and validate the JSON request body format.
  • Empty or malformed request body: Since the request body is required, ensure it is properly formatted JSON matching the API expectations for updating price book associated products.

Links and References


Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution or dynamic import resolution.

Discussion