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 Permissions" operation, it retrieves permission-related data from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

• Automating administrative tasks such as fetching user permissions.
• Integrating ScaleFluidly's permission management into workflows for access control audits.
• Synchronizing permissions data with other systems or dashboards.

For example, a workflow could use this node to fetch all permissions assigned to users in a given environment (Dev, QA, or Local) to verify compliance or trigger alerts if unauthorized permissions are detected.

Properties

Note: The "Environment" property selects the base URL for API requests, allowing the user to switch between development, quality assurance, or local instances of the ScaleFluidly service.

Output

The node outputs an array of JSON objects under the json output field. Each object corresponds to the response from the ScaleFluidly API for the requested operation. For the "Get Permissions" operation, the output will contain permission details retrieved from the Admin resource.

No binary data output is produced by this node.

Dependencies

• Requires access to the ScaleFluidly API endpoints corresponding to the selected environment.
• Optionally uses an API authentication token passed via HTTP headers (Bearer token). This token must be provided in the input data's headers.authorization field on the first item.
• No explicit external npm packages beyond n8n core dependencies are required.
• The node expects the user to configure credentials or provide authorization tokens externally.

Troubleshooting

• Bearer token not found error: If the input data does not include an authorization header with a Bearer token on the first item, the node will throw an error. Ensure that the token is correctly set in the input data or configured in the node credentials.
• Operation not found error: If the specified operation (intent) does not exist in the internal mapping, the node will fail. Verify that the operation name matches one of the supported Admin operations.
• API request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request errors. Check connectivity and authentication details.
• Empty or malformed request body: Some operations require a JSON request body; ensure the request_info parameter is correctly formatted.

Links and References

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

Note: Replace URLs above with the appropriate environment based on your selection.