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 with the Get Template List operation, it fetches a list of templates from the selected ScaleFluidly environment.

Common scenarios where this node is beneficial include:

• Automating retrieval of administrative data like user lists or templates.
• Integrating ScaleFluidly's admin functionalities into workflows for monitoring or reporting.
• Fetching template data dynamically to use in subsequent workflow steps.

For example, a user might configure this node to connect to the QA environment and retrieve all available templates to display or process them further in an automation pipeline.

Properties

Note: The node also requires selecting the Resource (Admin) and Operation (Get Template List), but these are fixed by your input context.

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 Template List" operation, this will typically be a list of template metadata objects retrieved from the API.

No binary data output is indicated in the source code.

Dependencies

• Requires access to the ScaleFluidly API endpoints corresponding to the chosen environment.
• Optionally uses an API authentication token passed via the HTTP Authorization header. This token must be provided in the input data's first item's JSON headers under authorization.
• No explicit internal credential type is required, but if no authorization header is found in the first input item, the node throws an error.
• The node supports using an n8n credential for ScaleFluidly API authentication if no direct bearer token is provided.

Troubleshooting

• Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no other authentication method is configured, the node will throw an error. Ensure that the input data includes a valid bearer token or configure the node with appropriate API credentials.
• Operation not found: If the specified operation is not mapped in the internal intent-to-URL map, the node will throw an error indicating the operation was not found. Verify that the operation name matches one of the supported operations.
• API request failures: Network issues, invalid tokens, or incorrect environment URLs can cause request failures. Check connectivity and credentials.
• Invalid JSON in Request Body: If the request_info parameter contains malformed JSON, the request may fail. Validate JSON syntax before running the node.

Links and References

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

If you need details on other resources or operations, please provide their names.