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 for the "Case" resource in this node allows users to retrieve multiple case records from the Binalyze AIR system. This operation is useful when you want to list or search through cases associated with one or more organizations, optionally filtering by status or searching by terms. Typical scenarios include:
- Fetching all cases for a specific organization to display in a dashboard.
- Retrieving open or closed cases for reporting or auditing purposes.
- Searching cases by keywords to find relevant investigations quickly.
- Paginating through large sets of cases to process them in batches.
For example, a security analyst might use this node to pull all open cases from a particular organization to prioritize incident response efforts.
Properties
| Name | Meaning |
|---|---|
| Organization | The organization(s) to which the cases belong. You can specify by selecting from a list, entering IDs (comma-separated), or by name. Use "0" to select all organizations. |
| Additional Fields | Optional parameters to refine the query: - Page Number: Which page of results to retrieve (default 1). - Page Size: Number of cases per page (default 20). - Search Term: Text to filter cases by matching content. - Filter By Status: Filter cases by their status; options are All, Open, Closed, Archived. |
Output
The output JSON contains an array of case objects matching the query criteria. Each case object typically includes details such as case ID, title, status, associated organization, creation date, and other metadata relevant to the case management system.
This node does not output binary data.
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.
- Pagination and filtering depend on the API's support for these features.
Troubleshooting
- Invalid Organization ID Format: If you enter organization IDs incorrectly (not comma-separated numbers or invalid characters), the node will throw a validation error. Ensure IDs are numeric and separated by commas, or use "0" for all organizations.
- No Cases Returned: If no cases appear, verify that the organization ID(s) are correct and that there are cases matching the filters (status, search term).
- API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access case data.
- Pagination Issues: Requesting a page number beyond the available range may return empty results. Adjust the page number accordingly.
Links and References
- Binalyze AIR Official Documentation
- Binalyze AIR API Reference (for detailed info on case endpoints)
- n8n Documentation on Creating Custom Nodes