ScaleFluidly

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various administrative and operational tasks by selecting a Resource and Operation. Specifically for the Admin - Get Functions operation, it fetches administrative function data from the ScaleFluidly environment specified (Dev, QA, or Local). This is useful for managing or retrieving metadata about available admin functions in different deployment environments.

Common scenarios include:

• Retrieving a list of administrative functions or capabilities available in a given environment.
• Automating administrative workflows by dynamically fetching function details.
• Integrating ScaleFluidly admin operations into broader automation pipelines.

Example: A user might select the "Admin" resource and "Get Functions" operation to retrieve all admin functions available in the Dev environment, then use that data to configure further automated steps.

Properties

The node also requires selecting:

• Resource: fixed as "Admin" for this context.
• Operation: fixed as "Get Functions" for this context.

No additional input properties are required for this operation beyond the environment selection.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested admin functions. Each item in the output corresponds to one function or related administrative data retrieved.

The exact structure depends on the API response but generally includes details such as function names, descriptions, permissions, or other metadata relevant to admin functions.

No binary data output is produced by this operation.

Dependencies

• Requires access to the ScaleFluidly API endpoint corresponding to the selected environment URL.
• Optionally uses an authorization bearer token extracted from the first input item's JSON headers if present; otherwise, it attempts to authenticate using configured API credentials.
• No internal credential names are exposed; users must provide appropriate API authentication tokens or credentials configured in n8n.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization header with a bearer token and no API credentials are configured, the node will throw an error. Ensure that either the input contains a valid bearer token or proper API credentials are set up.
• 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 supported admin operations.
• Network or authentication errors: Check environment URL correctness and API key/token validity.
• Empty or unexpected output: Confirm that the API endpoint is reachable and returns expected data for the selected environment.

Links and References

• ScaleFluidly API Documentation (QA environment)
• ScaleFluidly Dev Environment Docs
• For local testing: http://localhost:8400 (if running ScaleFluidly API locally)

These links correspond to the environment URLs selectable in the node properties.