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 Layout Fields By Object operation, the node fetches layout field information related to a specified object within the ScaleFluidly system.

Typical use cases include:

• Retrieving metadata about UI layouts or data structures configured in ScaleFluidly.
• Automating administrative tasks that require knowledge of object layouts.
• Integrating layout field data into workflows for dynamic form generation or validation.

For example, a user might want to get all layout fields associated with a "Quote" object to dynamically build a custom interface or validate incoming data against the expected fields.

Properties

Details on Properties:

• Environment: Selects which ScaleFluidly environment to target. Useful for testing (Dev), staging (QA), or local development.
• Request: A JSON input where you specify parameters or filters needed by the API endpoint for the operation. For "Get Layout Fields By Object," this would typically include identifiers or criteria to specify which object's layout fields to retrieve.

Output

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

• The json output contains the parsed JSON response from the API call.
• The structure depends on the API's response for the "Get Layout Fields By Object" operation, likely including details about each layout field such as field names, types, labels, visibility, and other metadata.
• No binary data output is indicated.

Dependencies

• Requires access to the ScaleFluidly API endpoints.
• Optionally uses an API authentication token if provided in the input data headers under authorization.
• The node supports using either direct bearer tokens passed in the input or credentials configured in n8n (an API key credential).
• The environment URLs must be reachable from the n8n instance.

Troubleshooting

• Bearer token not found: 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 input includes a valid bearer token or the node is configured with appropriate API credentials.
• Operation not found: 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 API errors: Standard HTTP errors may occur if the environment URL is incorrect, the API is down, or credentials are invalid. Check connectivity and authentication.
• Invalid JSON in Request property: The request_info property must be valid JSON matching the expected schema for the operation; otherwise, the API call may fail.

Links and References

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

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