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 Object Names Meta Data operation, the node fetches metadata about object names from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

• Retrieving metadata information for administrative purposes.
• Automating workflows that require up-to-date object metadata from ScaleFluidly.
• Integrating ScaleFluidly's admin data into other systems or processes.

For example, a user might use this node to programmatically obtain a list of object names and their metadata to dynamically build UI elements or validate data structures in an automated workflow.

Properties

Note: The node also requires selecting the Resource ("Admin") and Operation ("Get Object Names Meta Data"), but these are fixed by your selection and not exposed as input properties here.

Output

The node outputs an array of JSON objects under the json output field. Each object corresponds to the response from the ScaleFluidly API for the requested operation. For the "Get Object Names Meta Data" operation, the output will contain metadata details about object names retrieved from the API.

No binary data output is indicated for this operation.

Dependencies

• Requires access to the ScaleFluidly API endpoints corresponding to the selected environment.
• Optionally uses an API authentication token (bearer token) passed via the input data headers on the first item; if missing, the node throws an error.
• No explicit credential configuration is mandatory, but the node supports using an API key credential if configured.

Troubleshooting

• Bearer token not found: If the input data does not include an authorization header with a bearer token on the first item, the node will throw an error. Ensure the first input item contains a valid authorization token in json.headers.authorization.
• Operation not found: If the specified operation is not mapped internally, the node will throw an error indicating the operation is unknown. Verify the operation name matches one of the supported operations.
• Request failures: Network issues or incorrect environment URLs can cause request failures. Confirm the environment URL is correct and accessible.
• Invalid request body: Some operations require a JSON request body. Make sure the request_info parameter is correctly formatted JSON when required.

Links and References

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

If you need further details on other operations or resources, feel free to ask!