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 integrates with Binalyze AIR to manage various resources related to digital forensics and incident response. Specifically, the Case - Get Activities operation retrieves the activity logs or events associated with a particular case identified by its Case ID. This is useful for tracking all actions, changes, or updates made within a case, providing an audit trail and helping investigators understand the timeline and context of the investigation.
Practical examples:
- Automatically fetching recent activities on a case to update a dashboard.
- Triggering alerts or follow-up actions based on specific activities recorded in a case.
- Integrating case activity data into external reporting or ticketing systems.
Properties
| Name | Meaning |
|---|---|
| Case ID | The unique identifier of the case for which to retrieve activities. This is a required string input where you enter the specific Case ID. |
Output
The output JSON contains the list of activities related to the specified case. Each activity typically includes details such as timestamps, user actions, descriptions, and other metadata relevant to the case's event history.
If the node supports binary data output (not explicitly shown here), it would represent attachments or evidence files related to the activities, but this operation primarily returns structured JSON data about case activities.
Dependencies
- Requires an active connection to Binalyze AIR via an API key credential configured in n8n.
- The node depends on the Binalyze AIR API endpoints for cases and their activities.
- Proper permissions on the API key are necessary to access case information and activities.
Troubleshooting
Common issues:
- Invalid or missing Case ID: Ensure the Case ID provided exists and is correctly formatted.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check connectivity to the Binalyze AIR service.
Error messages:
"Unknown resource: cases": Occurs if the resource parameter is incorrectly set; ensure "cases" is selected.- API errors indicating unauthorized access or forbidden operations usually mean the API key lacks required scopes.
- Timeout or connection errors suggest network issues or service unavailability.
Links and References
- Binalyze AIR Official Documentation
- Binalyze AIR API Reference
- n8n documentation on Creating Custom Nodes