ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

The "Update Objects" operation within the Admin resource of this ScaleFluidly node allows users to send update requests to the ScaleFluidly API for various administrative objects. This operation is useful when you need to modify existing data records or configurations managed by the ScaleFluidly platform, such as updating user information, permissions, groups, or other admin-level entities.

Typical scenarios include:

  • Updating user details or roles in an administrative system.
  • Modifying configuration rules or approval workflows.
  • Adjusting group memberships or permissions dynamically.

For example, if you want to update a user's role or contact information stored in ScaleFluidly, you would use this operation with the appropriate request body describing the changes.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server).
Request JSON object representing the request body containing the update details for the admin objects. This must be structured according to the ScaleFluidly API's expected format for the specific update action.

Output

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

If the API returns binary data (not typical for update operations), it would represent files or attachments related to the updated objects, but this node primarily deals with JSON responses.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • An authorization token (Bearer token) must be provided in the input data headers or via configured credentials to authenticate API requests.
  • No explicit external libraries beyond n8n core helpers are required.

Troubleshooting

  • Bearer token not found: If the authorization header with a Bearer token is missing in the first input item's headers and no prior token is cached, the node will throw an error. Ensure that the first input item includes valid authorization headers or that credentials are properly set up.
  • Operation not found: If the operation name does not map to a known intent URL, an error will occur. Verify that the operation parameter is correctly set to "update_objects" under the Admin resource.
  • Invalid request body: Since the request body is a free-form JSON, malformed or incorrect data structures may cause API errors. Validate the JSON structure against ScaleFluidly API documentation before sending.
  • Environment URL issues: Selecting an incorrect environment or having network connectivity problems to the specified URL can cause request failures.

Links and References

Discussion