ScaleFluidlyInstall

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 Users Details operation, it retrieves detailed information about users managed by the ScaleFluidly system.

Typical use cases include:

• Fetching user details for administrative dashboards.
• Synchronizing user data between ScaleFluidly and other systems.
• Auditing or reporting on user accounts within an organization.

For example, an admin might use this node to pull a list of all users along with their profile details to display in a custom internal tool or to trigger workflows based on user attributes.

Properties

The node also requires selecting the Resource as "Admin" and the Operation as "Get Users Details" (internally represented as get_all_users), but these are fixed by your selection and not exposed as input properties here.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Users Details" operation, each object typically contains user-related fields such as user IDs, names, emails, roles, and other metadata provided by the API.

The output structure is:

[
  {
    "id": "string",
    "name": "string",
    "email": "string",
    "role": "string",
    "...": "other user details"
  },
  ...
]

No binary data output is produced by this operation.

Dependencies

• Requires an active connection to the ScaleFluidly API endpoint corresponding to the selected environment (Dev, QA, or Local).
• Needs an authorization token passed via the input data's headers.authorization field on the first item or uses stored credentials if configured.
• No explicit external credential type names are exposed; users must provide a valid bearer token for authentication.
• The node depends on n8n's HTTP request helper methods to communicate with the API.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no credentials are configured, the node will throw an error. Ensure that the token is provided either in the input data headers or via node credentials.
• Operation not found error: If the operation name does not map to a known API endpoint internally, the node will fail. This should not occur if using the provided UI options correctly.
• API request failures: Network issues, invalid tokens, or incorrect environment URLs can cause request errors. Verify the environment URL and token validity.
• Empty or malformed response: Check that the API endpoint is returning expected data and that the request body (if any) is correctly formatted.

Links and References

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

These links correspond to the environments selectable in the node properties.