ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

The ScaleFluidly node integrates with the ScaleFluidly API, enabling users to perform various operations across multiple resources such as Admin, Quote, Configure, Pricing, and MCP. Specifically, for the Admin resource and the Update Permission operation, this node allows updating permission settings within the ScaleFluidly system by sending a custom JSON request body.

This node is beneficial in scenarios where automated management of permissions is required, such as updating user roles or access rights programmatically within an organization's workflow. For example, it can be used to update permissions after organizational changes or to synchronize permissions with external systems.

Properties

Name Meaning
Environment The target environment for the API call. Options include:
- Dev (https://documentation-dev.scalefluidly.com)
- QA (https://documentation.scalefluidly.com)
- Local (http://localhost:8400)
Request A JSON object representing the request body to send for the Update Permission operation. This should contain all necessary data fields as expected by the ScaleFluidly API for updating permissions.

Output

  • The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item.
  • Each output JSON object contains the raw response data returned by the API after performing the Update Permission operation.
  • No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • Optionally uses an API authentication token if provided in the input data headers under authorization.
  • If no explicit authorization header is found in the first input item, the node attempts to use configured credentials named generically as "an API key credential" for authentication.
  • No additional external dependencies are required beyond standard HTTP request capabilities.

Troubleshooting

  • Bearer token not found error: This occurs if the first input item does not contain an authorization token in its headers and no API credential is configured. To resolve, ensure that either the first input includes a valid bearer token in the headers.authorization field or configure the node with appropriate API credentials.
  • Operation not found error: If the specified operation (intent) does not match any known operation 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-defined JSON, malformed or incomplete JSON may cause API errors. Validate the JSON structure before execution.
  • Environment URL issues: Ensure the selected environment URL is reachable and correct; network or URL misconfiguration can lead to connection failures.

Links and References


Note: This summary is based on static analysis of the node's source code and provided property definitions. Runtime behavior depends on actual API responses and configured credentials.

Discussion