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 operation retrieves multiple tasks from the Binalyze AIR system, filtered by various criteria such as organization, execution type, name, source, status, and type. It is useful for workflows that need to list or process batches of tasks related to digital forensics, incident response, or endpoint management.
Typical use cases include:
- Fetching all tasks for a specific organization or set of organizations.
- Filtering tasks by their current status (e.g., completed, failed) to trigger follow-up actions.
- Paging through large sets of tasks to process them incrementally.
- Narrowing down tasks by type or source to focus on particular operations like acquisitions or investigations.
Properties
| Name | Meaning |
|---|---|
| Organization | Select one or more organizations to filter tasks. Use "0" to select all organizations, specify comma-separated numeric IDs for multiple organizations, or search by organization name for a single organization. |
| Additional Fields | Optional filters and pagination settings: - Filter By Execution Type: Filter tasks by when they execute ("Now", "Scheduled"). - Filter By Name: Partial match filter on task names. - Filter By Source: Filter by task origin ("API", "Scheduler", "System", "User", "Webhook"). - Filter By Status: Filter by task status ("Assigned", "Cancelled", "Completed", "Failed", "Processing", "Scheduled"). - Filter By Type: Filter by task type (e.g., "Acquire Image", "Investigation", "Reboot", etc.). - Page Number: Which page of results to return (minimum 1). - Page Size: Number of results per page (minimum 1). |
Output
The node outputs an array of task objects in the json field. Each object represents a task with its properties as returned by the Binalyze AIR API. The exact structure depends on the API but typically includes identifiers, status, type, execution details, and metadata about each task.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Binalyze AIR API using a configured API authentication credential.
- The node depends on the Binalyze AIR service being accessible and the user having appropriate permissions to query tasks.
- Pagination parameters allow handling large result sets efficiently.
Troubleshooting
- Invalid Organization IDs: If organization IDs are not numeric or improperly formatted, the node may throw validation errors. Ensure IDs are comma-separated numbers or use "0" for all organizations.
- Empty Results: Applying overly restrictive filters may result in no tasks returned. Try broadening filters or verifying the existence of tasks matching criteria.
- API Authentication Errors: If the API key or token is invalid or expired, the node will fail to retrieve tasks. Verify credentials and permissions.
- Pagination Issues: Requesting a page number beyond available pages may return empty results. Adjust page number accordingly.
- Unknown Resource Error: This error indicates the resource parameter is incorrect; ensure "tasks" is selected for this operation.
Links and References
- Binalyze AIR Official Documentation
- Binalyze AIR API Reference
- n8n Documentation on Creating Custom Nodes