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 Groups operation, the node fetches group-related data from the ScaleFluidly system.

Typical use cases include:

• Retrieving lists of user groups or organizational groups within ScaleFluidly.
• Managing access control or permissions by analyzing group memberships.
• Automating workflows that depend on group information, such as assigning tasks or notifications based on group membership.

For example, a user might use this node to get all groups in their environment to dynamically assign roles or permissions in another system.

Properties

Details:

• Environment: Selects which ScaleFluidly API endpoint to use. This allows switching between development, quality assurance, or local testing environments.
• Request: A JSON input that contains any additional parameters required by the API call. For "Get Groups," this may be empty or contain filters depending on API specifics.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Groups" operation, the output JSON typically includes details about each group, such as group IDs, names, descriptions, and possibly member counts or other metadata.

If the API returns binary data (not typical for "Get Groups"), it would be included in the binary output field, but this operation primarily deals with JSON data.

Dependencies

• Requires access to the ScaleFluidly API endpoints specified by the selected environment.
• Optionally uses an API authentication token (bearer token) passed via HTTP headers. The token is extracted from the first input item's JSON headers if present.
• No explicit external npm packages beyond n8n's standard helpers are required.
• The node expects the user to configure credentials or provide authorization tokens appropriately.

Troubleshooting

• Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no prior token was stored, the node will throw an error. Ensure the token is provided in the input or configured in credentials.
• Operation not found: If the operation name does not map to a known API endpoint, an error is thrown. Verify the operation parameter matches one of the supported operations.
• API connectivity issues: Network errors or incorrect environment URLs can cause failures. Confirm the environment URL is reachable and correct.
• Invalid JSON in Request property: Malformed JSON in the "Request" property can cause the API call to fail. Validate JSON syntax before execution.

Links and References

• ScaleFluidly API Documentation (QA environment URL)
• n8n Documentation on Creating Custom Nodes
• General REST API usage patterns in n8n: HTTP Request Node

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