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 Products operation, it fetches product-related data from the ScaleFluidly platform.

Common scenarios where this node is beneficial include:

• Retrieving product lists or details for administrative purposes.
• Automating workflows that require up-to-date product information from ScaleFluidly.
• Integrating ScaleFluidly product data into other systems or dashboards.

For example, a user might use this node to automatically pull all products managed in ScaleFluidly into a CRM system or to trigger alerts when new products are added.

Properties

The Environment property lets you select which ScaleFluidly environment to connect to:

• Dev: Development environment URL.
• QA: Quality Assurance environment URL.
• Local: Localhost instance URL (for local testing).

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. Each item corresponds to the data returned by the API call, typically including product details when using the Admin resource's Get Products operation.

If the API returns binary data (not indicated in this code), it would be included accordingly, but this node primarily handles JSON responses.

Dependencies

• Requires access to the ScaleFluidly API endpoint specified by the selected environment.
• Optionally uses an API authentication token passed via the authorization header in the input data.
• If no explicit authorization header is found in the first input item, the node expects an API key credential configured in n8n under a generic API authentication method.
• No other external dependencies are required.

Troubleshooting

• Bearer token not found: This error occurs if the node cannot find an authorization token in the input headers and no API credential is configured. To fix, ensure the first input item includes an authorization header with a valid bearer token or configure the API credentials properly.
• Operation "X" not found: Indicates the requested operation does not exist in the internal mapping. Verify the operation name matches one of the supported operations for the selected resource.
• Request failures: Network issues or incorrect environment URLs can cause request errors. Confirm the environment URL is correct and accessible.
• Invalid JSON in Request Body: If providing a custom request body (request_info), ensure it is valid JSON.

Links and References

• ScaleFluidly API Documentation (QA environment)
• n8n Documentation on HTTP Request Node (for understanding how API requests work in n8n)

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