ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

The "Update Users" operation within the Admin resource of the ScaleFluidly node allows users to update user information by sending a custom JSON request body to the ScaleFluidly API. This node acts as a flexible interface to interact with various ScaleFluidly API endpoints, specifically here for administrative user updates.

Common scenarios where this node is beneficial include:

  • Automating user management tasks such as updating user roles, permissions, or profile details in bulk.
  • Integrating ScaleFluidly user administration into broader workflows, e.g., syncing user data from other systems.
  • Customizing user attributes dynamically based on workflow logic.

For example, a workflow could trigger when a new employee joins and automatically update their user profile in ScaleFluidly with relevant department and access level information.

Properties

Name Meaning
Environment The target environment URL for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). Determines which ScaleFluidly instance the request targets.
Request A JSON object representing the request body sent to the API for updating users. This must be provided and should conform to the expected API schema for user updates.

Output

The node outputs an array of JSON objects corresponding to the responses received from the ScaleFluidly API for each input item processed. Each JSON object contains the API response data related to the user update operation.

If the API returns binary data (not typical for this operation), it would be included accordingly, but primarily the output is structured JSON reflecting success, errors, or updated user details.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • May require an API authentication token (bearer token) passed via HTTP headers; this token is extracted from the first input item's JSON headers.authorization field or managed internally if configured.
  • No explicit external credential type names are exposed; users must ensure valid authorization tokens are available in the workflow context.

Troubleshooting

  • Bearer token not found: If the authorization header is missing in the first input item, the node throws an error. Ensure that the first input includes a valid bearer token in json.headers.authorization.
  • Operation not found: If the operation name does not map to a known intent URL, an error is thrown. Confirm the operation parameter is correctly set to "update_users" for this use case.
  • Invalid JSON request body: The request_info property must be a valid JSON object matching the API's expected schema. Malformed or incomplete JSON will cause API errors.
  • API connectivity issues: Verify the selected environment URL is reachable and correct, especially when using local or dev environments.
  • Permission errors: Ensure the API token has sufficient privileges to perform user updates.

Links and References

  • ScaleFluidly API Documentation (QA environment)
  • Refer to your organization's ScaleFluidly API specification for detailed request body schemas and user update rules.

Discussion