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 endpoint assets, specifically allowing users to add tags to selected assets. This operation is useful for organizing and categorizing assets based on custom tags, which can help in filtering, reporting, or triggering further automated workflows.
Typical use cases include:
- Tagging newly discovered assets automatically after an acquisition.
- Adding classification tags (e.g., "critical", "needs review") to assets based on external criteria.
- Grouping assets by environment, department, or project using tags for easier management.
Properties
| Name | Meaning |
|---|---|
| Tags | Comma-separated list of tags to add to the selected assets. Example: tag1,tag2,tag3. |
| Filter Options | Collection of filters to select which assets to tag. Filters include: - Excluded Asset IDs: comma-separated asset IDs to exclude. - Filter By Asset Name: filter assets by name. - Filter By IP Address. - Filter By Isolation Status: options are "Isolated" or "Not Isolated". - Filter By Managed Status: options are "Managed" or "Unmanaged". - Filter By Online Status: options are "Online" or "Offline". - Filter By Organization: select organization by list, ID, or name. - Filter By Platform: options are "Windows", "macOS", "Linux". - Filter By Search Term. - Filter By Tags: comma-separated tags. - Included Asset IDs: comma-separated asset IDs to explicitly include. |
Output
The node outputs JSON data representing the result of the tagging operation on the selected assets. The exact structure depends on the underlying API response but typically includes information about which assets were tagged successfully and any errors encountered.
If binary data output is supported, it would represent related files or reports, but this operation primarily deals with JSON metadata about assets and tags.
Dependencies
- Requires a valid API authentication token credential for Binalyze AIR.
- The node depends on the Binalyze AIR API being accessible and properly configured.
- No additional external services are required beyond the Binalyze AIR platform.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing invalid asset IDs in included or excluded lists may result in no assets being tagged.
- Using filters that do not match any assets will result in no changes.
- Network connectivity issues to the Binalyze AIR API will cause execution errors.
Error Messages:
"Unknown resource: assets"— indicates the resource parameter was not set correctly.- API errors returned from Binalyze AIR (e.g., unauthorized, bad request) should be checked for correct credentials and valid input parameters.
Resolution Tips:
- Verify API credentials and permissions.
- Double-check filter values and asset IDs.
- Ensure network access to the Binalyze AIR API endpoint.
- Use logging/debugging to inspect the exact request payload sent.
Links and References
- Binalyze AIR Official Documentation
- Binalyze AIR API Reference
- n8n Documentation on Creating Custom Nodes