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 "Get Many" operation under the "Acquisition" resource in this node is designed to retrieve multiple acquisition records from Binalyze AIR. This operation is useful for workflows that need to list or process batches of acquisition profiles or remote acquisitions, such as auditing endpoint data collections, monitoring ongoing acquisitions, or integrating acquisition metadata into broader incident response processes.
Practical examples include:
- Fetching a list of recent acquisitions to display in a dashboard.
- Automating reports on acquisition activities filtered by organization or other criteria.
- Integrating acquisition data with case management or evidence handling workflows.
Properties
| Name | Meaning |
|---|---|
| Filter By Organization | Select one or more organizations to filter acquisitions by their associated organizations. |
| Limit | Maximum number of acquisition results to return (minimum 1, default 50). |
Note: The "Additional Fields" collection includes various filters and options relevant to other operations but for "Get Many" only the "Filter By Organization" and "Limit" fields are applicable.
Output
The output consists of JSON objects representing acquisition records retrieved from the system. Each item in the output array corresponds to an acquisition profile or remote acquisition entry, containing details such as acquisition metadata, status, timestamps, and related organizational information.
This node does not output binary data for this operation.
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.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Specifying invalid organization IDs in the filter may result in empty results or errors.
- Requesting a very high limit might lead to performance issues or API rate limiting.
Error Messages:
"Unknown resource: acquisitions"— indicates the resource parameter was set incorrectly; ensure it is exactly "acquisitions".- API errors related to authentication or permissions typically indicate issues with the provided API key or user rights.
Resolutions:
- Verify API credentials and permissions.
- Use valid organization IDs obtained from the organizations list.
- Adjust the limit parameter to a reasonable number.
Links and References
- Binalyze AIR Official Documentation
- n8n Expressions Documentation (for dynamic input values)