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 Group Members operation, the node fetches members of a specified group from the ScaleFluidly system.

Typical use cases include:

• Retrieving user lists within specific groups for administrative or reporting purposes.
• Automating workflows that require group membership data, such as permission management or notifications.
• Integrating group member data into other systems or dashboards.

For example, an admin might use this node to get all members of a sales team group to send targeted communications or analyze team composition.

Properties

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the Get Group Members operation, the output JSON will contain details about each member in the specified group, such as user IDs, names, roles, or other metadata provided by the API.

If the API returns binary data (not typical for this operation), it would be included accordingly, but primarily the output is structured JSON data reflecting group membership information.

Dependencies

• Requires access to the ScaleFluidly API endpoint corresponding to the chosen environment.
• Optionally uses an API authentication token (bearer token) passed via HTTP headers for authorized requests.
• The node supports using an n8n credential for authentication if configured; otherwise, it expects the bearer token to be present in the input data headers.
• No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

• Bearer token not found error: 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 API key credential is set up in n8n or the authorization token is included in the input data headers.
• Operation not found error: If the operation name does not match any known intent URL mapping, the node will report that the operation is not found. Verify that the operation parameter is correctly set to "get_group_members" for this use case.
• API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause HTTP errors. Check the environment selection and the structure of the JSON request body.
• Empty or unexpected responses: Confirm that the group identifier or parameters in the request JSON are correct and that the group exists in the ScaleFluidly system.

Links and References

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

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