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
This node integrates with Binalyze AIR to manage acquisition tasks, specifically enabling the creation of off-network acquisition tasks within a digital forensics or incident response workflow. It is useful when you need to assign acquisition jobs that are performed outside the network environment, such as manual evidence collection or remote acquisitions that do not rely on direct network connectivity.
Typical use cases include:
- Creating and assigning off-network acquisition tasks to specific cases.
- Specifying acquisition profiles and organizations responsible for the task.
- Managing task metadata like name and description to track acquisition efforts.
For example, a security analyst can automate the creation of an off-network acquisition task linked to a case, specifying which acquisition profile to use and which organization will handle the task, streamlining evidence collection workflows.
Properties
| Name | Meaning |
|---|---|
| Case | The case to assign the acquisition task to. Can be selected from a list of cases or specified by ID. |
| Acquisition Profile | The acquisition profile to use for the task. Selectable from existing profiles or by ID. |
| Task Name | The name of the off-network acquisition task. |
| Task Description | A textual description providing details about the off-network acquisition task. |
| Organization | The organization responsible for the off-network acquisition task. Can be selected from a list, by numeric ID, or by name. |
Output
The node outputs JSON data representing the created off-network acquisition task. This typically includes details such as the task identifier, associated case, acquisition profile, organization, task name, description, status, and timestamps. The output allows downstream nodes or workflows to process or log the newly created task information.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Binalyze AIR platform.
- The node depends on Binalyze AIR's REST API endpoints for acquisitions, cases, acquisition profiles, and organizations.
- Proper configuration of the API authentication in n8n credentials is necessary.
- Network access to the Binalyze AIR service endpoint must be available.
Troubleshooting
- Invalid Case or Acquisition Profile ID: If the provided case or acquisition profile ID does not match expected patterns (only letters, numbers, hyphens, underscores), the node will reject the input. Ensure IDs conform to the required format.
- Organization ID Validation: Organization IDs must be numeric if entered manually; otherwise, select from the list or specify by name.
- API Authentication Errors: Failure to authenticate with the Binalyze AIR API will prevent task creation. Verify that the API key credential is correctly configured and has sufficient permissions.
- Missing Required Fields: The node requires all mandatory fields (case, acquisition profile, task name, organization) to be set. Omitting any will cause errors.
- Network Connectivity Issues: Ensure that the n8n instance can reach the Binalyze AIR API endpoint without firewall or proxy issues.