ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API to perform various operations across multiple resources, including Admin, Quote, Configure, Pricing, and MCP. Specifically, for the Admin resource with the Get All Groups operation, it retrieves a list of all user groups from the ScaleFluidly system.

This node is useful in scenarios where you need to programmatically access administrative data such as user groups for management, reporting, or automation purposes. For example, an admin might use this node to fetch all groups to synchronize them with another system or to audit group memberships.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local (localhost).
  • Environment selects which ScaleFluidly API endpoint to interact with, allowing users to switch between development, quality assurance, or local testing environments.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get All Groups" operation under the Admin resource, the output JSON contains details about each group retrieved, such as group IDs, names, and possibly other metadata depending on the API response.

The output is structured as:

[
  {
    "groupId": "...",
    "groupName": "...",
    ...
  },
  ...
]

No binary data output is involved in this operation.

Dependencies

  • Requires access to the ScaleFluidly API endpoints specified by the selected environment.
  • Optionally uses an API authentication token passed via the input data's authorization header or through configured credentials.
  • No explicit internal credential type names are exposed; users must provide a valid bearer token either in the input data headers or via n8n credentials configured for the ScaleFluidly API.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no token is stored in static workflow data, the node will throw an error. Ensure that the input data includes a valid authorization token or configure the API credentials properly.
  • 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 that the operation parameter is correctly set to "get_groups" for fetching all groups.
  • API request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request failures. Check connectivity, environment selection, and token validity.

Links and References


This summary focuses on the Admin resource's Get All Groups operation as requested, based on static analysis of the provided source code and property definitions.

Discussion