ScaleFluidlyInstall

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 Add Pricebook to a Category operation, the node enables adding a pricebook to a specified category within the ScaleFluidly system.

Common scenarios where this node is beneficial include automating the management of pricing structures by programmatically associating pricebooks with product categories. For example, a sales operations team could use this node in an automation workflow to update pricing configurations dynamically when new pricebooks are created or categories are modified.

Properties

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API calls made during execution. Each item in the output array contains the JSON response from the API for each input item processed.

• The json field holds the parsed JSON response from the ScaleFluidly API.
• If the API returns binary data (not indicated in this operation), it would be handled accordingly, but for this operation, only JSON responses are expected.

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 under authorization.
• No explicit external npm packages beyond standard n8n workflow helpers are required.
• The node expects the user to provide valid authorization credentials either via input data headers or configured credentials in n8n.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no prior authorization header was stored, the node will throw an error. Ensure that the input data includes a valid bearer token in the headers or configure the API credentials properly.
• Operation not found error: If the operation name (intent) does not match any known operation URL mapping, the node will throw an error indicating the operation is not found. Verify that the operation name is correct and supported.
• Invalid request body: Since the request body is user-provided JSON, malformed or incomplete JSON may cause API errors. Validate the JSON structure before running the node.
• Environment URL issues: Selecting an incorrect environment URL or having network connectivity issues to the chosen environment will result in request failures.

Links and References

• ScaleFluidly API Documentation (QA environment)
• Refer to your organization's ScaleFluidly API documentation for detailed schema of the request body for "Add Pricebook to a Category" operation.
• n8n Documentation on HTTP Request Node for understanding how API requests are structured in workflows.