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 Update Groups operation, the node sends a custom JSON request body to update group information within the ScaleFluidly system.

Typical use cases include automating administrative tasks related to user groups, such as modifying group memberships or updating group properties in an enterprise environment managed by ScaleFluidly. For example, a user might update permissions or attributes of a group programmatically as part of a workflow triggered by organizational changes.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). This determines which ScaleFluidly instance the request is sent to.
Request A JSON object representing the request body to be sent to the ScaleFluidly API for the selected operation. This must conform to the expected schema for the "update_groups" operation under the Admin resource.

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed. Each output JSON object contains the data returned by the API after performing the requested operation (e.g., confirmation of group updates or details of the updated groups).

If the API returns binary data (not indicated in this case), it would be included accordingly, but here the output is purely JSON-based.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • Optionally uses an API authentication token passed via an authorization header. The node attempts to extract a bearer token from the first input item's JSON headers or falls back to configured credentials if available.
  • No explicit external libraries beyond n8n's standard HTTP request helpers are required.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token and no credential is configured, the node will throw an error. Ensure that either the input includes a valid authorization token or the node is configured with appropriate API credentials.
  • Operation not found error: If the operation name provided does not match any known intent URL mapping, the node will throw an error indicating the operation was not found. Verify that the operation name is correct and supported.
  • Invalid request body: Since the request body is user-provided JSON, malformed or incorrect data may cause API errors. Validate the JSON structure against the ScaleFluidly API documentation for the "update_groups" operation.
  • Environment URL issues: Selecting an incorrect environment or having network connectivity problems to the specified URL can cause request failures.

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