Binalyze AIR icon

Binalyze AIR

Manage Binalyze AIR resources

Actions99

Overview

This node allows you to update an existing case in the Binalyze AIR system. It is useful for workflows that need to modify case details such as changing the case name, updating notes, assigning a new owner, or altering the status and visibility of a case. For example, you might use this node to automate case management by updating case statuses based on external triggers or to assign cases to different users dynamically.

Properties

Name Meaning
Case ID The unique identifier of the case you want to update.
Update Fields A collection of fields to update on the case:
   Name The new name for the case.
   Notes JSON array representing notes associated with the case.
   Owner User The new owner user for the case. Can be selected from a list, specified by user ID, or by username/email.
   Status The status of the case. Options: "Open", "Closed", "Archived".
   Visibility The visibility level of the case. Options: "Public to Organization", "Private to Users".

Output

The node outputs JSON data representing the updated case object after the update operation completes. This typically includes all the case properties reflecting the new state after modification. There is no binary output.

Dependencies

  • Requires an API key credential for authenticating with the Binalyze AIR API.
  • The node depends on the Binalyze AIR service being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Invalid Case ID: If the provided Case ID does not exist or is malformed, the node will likely throw an error indicating the case could not be found. Verify the Case ID is correct.
  • Permission Issues: Updating a case may fail if the API key used lacks sufficient permissions. Ensure the API key has rights to modify cases.
  • Invalid Owner User: When specifying a new owner user, ensure the user exists and the ID or username format is valid (alphanumeric, hyphens, underscores).
  • Malformed Notes JSON: The notes field expects a JSON array. Providing invalid JSON will cause errors. Validate the JSON structure before input.
  • Unsupported Status or Visibility Values: Only the predefined options are accepted. Using unsupported values will result in validation errors.

Links and References

Discussion