ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

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 Users operation, the node fetches user information associated with a particular group within the ScaleFluidly system.

Common scenarios where this node is beneficial include:

  • Retrieving members of a user group for administrative or reporting purposes.
  • Automating workflows that require knowledge of group membership, such as sending notifications or managing permissions.
  • Integrating ScaleFluidly user data into other systems or dashboards.

For example, an admin might use this node to get all users in a sales team group to send them targeted updates or synchronize their access rights.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local
Request JSON object containing the request body parameters specific to the operation (e.g., group ID)

Details:

  • Environment: Selects which ScaleFluidly API environment to interact with.
  • Request: A JSON input that must contain the necessary parameters for the "Get Group Users" operation, typically including identifiers like group IDs or filters required by the API endpoint.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Group Users" operation, the output JSON will typically include details about each user in the specified group, such as user IDs, names, roles, and contact information.

If the API returns binary data (not typical for this operation), it would be included accordingly, but this operation primarily deals with JSON user data.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API key credential configured in n8n for authenticated requests.
  • The node expects the authorization token to be provided either in the input data headers or via the configured credentials.
  • No additional external dependencies beyond standard HTTP requests.

Troubleshooting

  • Bearer token not found: This error occurs if the authorization header is missing in the first input item and no stored authorization header exists. Ensure that the input data includes a valid bearer token in the headers.authorization field or configure the API credentials properly.
  • Operation not found: If the specified operation does not match any known intent URL mapping, the node throws an error. Verify that the operation name is correct and supported.
  • Invalid JSON in Request: The request_info property must be a valid JSON object matching the expected API schema. Malformed JSON or missing required fields can cause API errors.
  • Network or API errors: Check connectivity to the selected environment URL and ensure the API service is operational.

Links and References


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

Discussion