ScaleFluidly

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 Non-Associated Pricebooks operation, the node fetches pricebooks that are not currently associated with a given category or entity within the ScaleFluidly system.

Common scenarios where this node is beneficial include:

• Managing pricing structures by identifying pricebooks available for association but not yet linked.
• Automating administrative tasks related to pricebook management in sales or product catalogs.
• Integrating ScaleFluidly's pricing data into workflows for further processing or reporting.

For example, a user might want to retrieve all pricebooks not linked to a specific product category to decide which pricebooks to associate next.

Properties

Output

The node outputs an array of JSON objects corresponding to the response from the ScaleFluidly API for the requested operation. Each item in the output array represents data returned by the API call, typically including details about non-associated pricebooks such as their IDs, names, and other metadata.

If the API returns binary data (not indicated here), it would be included accordingly, but for this operation, the output is expected to be purely JSON.

Dependencies

• Requires access to the ScaleFluidly API endpoints.
• An API authentication token (bearer token) must be provided via the input data headers on the first item or through configured credentials.
• The node uses the selected environment URL to construct the API request.
• No explicit external npm packages beyond n8n core helpers are required.

Troubleshooting

• Bearer token not found: If the authorization header with a bearer token is missing in the first input item's JSON headers, the node will throw an error. Ensure the token is correctly passed in the input data or configured credentials.
• Operation not found: If the specified operation does not exist in the internal intent-to-URL mapping, an error will be thrown. Verify the operation name matches one of the supported operations.
• API request failures: Network issues, invalid tokens, or incorrect request bodies can cause API errors. Check the environment URL, token validity, and request JSON structure.
• Empty or malformed request_info: The request body must be valid JSON matching the API expectations; otherwise, the API may reject the request.

Links and References

• ScaleFluidly API Documentation (QA environment)
• ScaleFluidly Developer Portal (Dev environment)

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