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 Get Layout Fields operation, the node sends a request to retrieve layout field information from the ScaleFluidly platform.

Typical use cases include:

• Fetching metadata about UI layouts or data fields configured in ScaleFluidly.
• Automating administrative tasks related to layout configurations.
• Integrating layout field data into workflows for dynamic form generation or validation.

For example, a user might want to dynamically fetch layout fields to customize a user interface or validate input data against the current layout schema.

Properties

The Request property is required and must be provided as a JSON object. It contains the necessary parameters for the "Get Layout Fields" operation (or any other selected operation). The exact structure depends on the ScaleFluidly API specification for that operation.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation.

• The json output field contains the parsed JSON response from the API call.
• If the API returns binary data (not typical for this operation), it would be included accordingly, but this node primarily handles JSON responses.

Dependencies

• Requires access to the ScaleFluidly API endpoint corresponding to the chosen environment.
• Optionally uses an API authentication token passed via the Authorization header. This token is extracted from the first input item's JSON headers or can be overridden per request.
• No internal credential names are exposed; users must provide valid authorization tokens as needed.
• The node relies on n8n's HTTP request helper methods to communicate with the ScaleFluidly API.

Troubleshooting

• Bearer token not found: If the first input item does not contain an authorization token in its headers, and no alternative token is provided, the node will throw an error. Ensure the input includes a valid bearer token in the authorization header.
• Operation not found: If the specified operation name does not match any known operation in the intent-to-URL mapping, the node will error out. Verify the operation name is correct and supported.
• Invalid JSON in Request: The Request property must be valid JSON. Malformed JSON will cause the API call to fail.
• Environment URL issues: Selecting an incorrect or unreachable environment URL will result in network errors. Confirm the environment setting matches your deployment.

Links and References

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

Note: Replace URLs with your actual ScaleFluidly API documentation links if different.