ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as Admin, Quote, Configure, Pricing, MCP, and Product. Specifically for the Admin resource with the Get Product Options operation, it fetches product option data from the ScaleFluidly backend.

Typical use cases include:

• Retrieving detailed product options for administrative purposes.
• Automating workflows that require up-to-date product configuration data.
• Integrating product option retrieval into larger automation pipelines for inventory or catalog management.

For example, a user might configure this node to pull all available product options in a QA environment to sync with an internal database or to display options dynamically in a custom UI.

Properties

Note: The node also requires selecting the Resource (Admin) and Operation (Get Product Options), but these are fixed by your input context.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. Each item in the output corresponds to the data returned by the API call for product options.

• The json field contains the parsed JSON response from the API.
• No binary data output is indicated for this operation.

The exact structure of the JSON depends on the ScaleFluidly API's response schema for product options, typically including details like option IDs, names, values, and related metadata.

Dependencies

• Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
• May optionally use an API authentication token if provided in the input data headers (authorization bearer token).
• No explicit external npm packages beyond n8n core dependencies are required.
• The node supports using an API key credential configured in n8n for authenticated requests, but can also work with bearer tokens passed dynamically via input data.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no stored authorization header exists, the node will throw an error. Ensure the input data includes valid authorization or configure credentials properly.
• Operation not found error: If the operation name does not map to a known intent URL, the node throws an error indicating the operation is invalid. Verify the operation parameter matches supported operations.
• API request failures: Network issues, incorrect environment URLs, or invalid tokens may cause HTTP errors. Check environment selection and authentication details.
• Empty or malformed response: Confirm the API endpoint is correct and the request body (if any) is properly formatted.

Links and References

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

If you need further details about other operations or resources, please provide their names.