ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as quotes, configuration, pricing, admin, and MCP (a custom module). Specifically, for the Configure resource and the Get Categories operation, the node fetches category-related data from the configured ScaleFluidly environment.

Typical use cases include:

• Retrieving product categories or configuration categories to dynamically populate UI elements.
• Automating workflows that depend on category data for further processing or decision-making.
• Integrating ScaleFluidly's configuration management into broader automation pipelines.

For example, a user might want to get all product categories available in a specific environment (Dev, QA, or Local) to update an internal catalog or synchronize with another system.

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 one response per input item processed.

• The json field contains the parsed JSON response from the API, typically including category details such as IDs, names, descriptions, and other metadata depending on the API's response schema.
• If the API supports binary data for this operation (not indicated here), it would be included accordingly, but for "Get Categories," the output is expected to be purely JSON.

Dependencies

• Requires access to the ScaleFluidly API endpoint specified by the selected environment.
• Optionally uses an API authentication token passed via the authorization header if present in the first input item's headers.
• No explicit external npm packages beyond n8n core helpers are required.
• The node can optionally use an API credential configured in n8n for authenticated requests.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization header with a bearer token and no credential is configured, the node will throw an error. Ensure that either the first input includes a valid bearer token in its headers or configure the node with appropriate API credentials.
• 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 name matches one of the supported operations.
• Network or environment URL issues: Make sure the selected environment URL is reachable and correct. Local environments require the local server to be running.
• Malformed JSON in Request property: The request_info JSON must be well-formed; otherwise, the API call may fail or return errors.

Links and References

• ScaleFluidly API Documentation (QA environment)
• ScaleFluidly Developer Portal (Dev environment)
• n8n Documentation on HTTP Request Node for understanding how API calls are made within n8n nodes.