Actions99
- InterACT Actions
- Notification Actions
- Organization Actions
- Task Actions
- Policy Actions
- Repository Actions
- Setting Actions
- Triage Rule Actions
- User Actions
- Acquisition Actions
- API Token Actions
- Asset Actions
- Auto Asset Tag Actions
- Baseline Actions
- Case Actions
- Evidence Actions
Overview
The node provides integration with Binalyze AIR to manage various resources, including cases. Specifically, the "Close Case" operation under the "Case" resource allows users to programmatically close an existing case by specifying its ID. This is useful in automated workflows where case lifecycle management is required, such as closing investigation cases after resolution or archiving completed incidents.
Practical examples:
- Automatically close a case when all related tasks are marked complete.
- Close cases based on external triggers or alerts from other systems.
- Integrate case closure into broader incident response automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Case ID | The unique identifier of the case to be closed. Users must provide this ID to specify which case should be closed. |
Output
The node outputs JSON data representing the result of the "Close Case" operation. Typically, this includes confirmation that the case was successfully closed and may include updated case details such as status, timestamps, or metadata reflecting the closure.
If the node supports binary data output (not indicated here), it would typically relate to attachments or evidence files associated with the case, but for the "Close Case" operation, the output is primarily JSON confirming the action.
Dependencies
- Requires an API key credential for authenticating with the Binalyze AIR service.
- The node depends on the Binalyze AIR API being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Case ID will likely cause the operation to fail.
- Network connectivity problems or incorrect API credentials can prevent successful communication with the Binalyze AIR service.
- Attempting to close a case that is already closed or in an incompatible state might result in errors.
Error messages and resolutions:
- "Unknown resource" error indicates the resource parameter is incorrect; ensure "cases" is selected.
- Authentication errors suggest checking the API key credential configuration.
- Validation errors about the Case ID mean verifying the ID exists and is correctly formatted.
Links and References
- Binalyze AIR Official Documentation
- Binalyze AIR API Reference
- n8n Documentation on Creating Custom Nodes