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 with the Add Objects operation, the node sends a JSON request body to the ScaleFluidly API endpoint corresponding to adding objects in the admin context.

Typical use cases include automating administrative tasks like adding new entities or records within the ScaleFluidly platform, which can be part of workflows that manage user permissions, configurations, or other administrative data. For example, an automation could add new user groups or permissions by sending the appropriate object data through this node.

Properties

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each output JSON corresponds to the API response for the respective request sent.

If the API returns binary data (not indicated explicitly here), it would be included accordingly, but based on the static analysis, the output is primarily JSON data reflecting the result of the add objects operation.

Dependencies

• Requires access to the ScaleFluidly API endpoints.
• Optionally uses an API authentication token passed via an authorization header. If the first input item contains an authorization token in its headers, it will be reused for subsequent requests.
• No explicit internal credential names are exposed; users must provide valid API tokens or credentials configured in n8n for authentication.
• The node depends on the request helper methods provided by n8n for HTTP communication.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization token in its headers and no other authentication method is configured, the node will throw an error indicating the missing bearer token. Ensure that the first input includes a valid authorization header or configure the node with proper API credentials.
• Operation not found error: If the specified operation (intent) does not match any known API endpoint mapping, the node will throw an error stating the operation was not found. Verify that the operation name is correct and supported.
• Invalid JSON in Request property: Since the request body is user-provided JSON, malformed JSON will cause the API call to fail. Validate the JSON structure before execution.
• Environment URL issues: Selecting an incorrect environment may lead to connection failures. Confirm the environment matches the intended API server.

Links and References

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

This summary focuses on the Admin resource's Add Objects operation as requested, describing how the node constructs and sends the request, handles authentication, and processes the response.