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 interacts with the Binalyze AIR platform to manage various resources, including Auto Asset Tags. Specifically, for the "Auto Asset Tag" resource and the "Get Many" operation, it retrieves multiple auto asset tags from the system. This is useful in scenarios where you want to list or filter tags that are automatically assigned to assets within an organization or across organizations.
Practical examples include:
- Fetching all auto asset tags visible to a default or specific organization.
- Searching for tags by name or partial match.
- Paginating through large sets of tags to process or display them incrementally.
This operation helps automate asset management workflows by integrating tag data into n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional filters and pagination controls: - Organization: Filter tags visible to all organizations (default 0) or a specific organization by selecting from a list, entering ID, or name. - Page Number: Which page of results to return (minimum 1). - Page Size: Number of results per page (minimum 1). - Search Term: Text to filter auto asset tags by name or content. |
Output
The node outputs JSON data containing the list of auto asset tags retrieved based on the input filters. Each item in the output typically represents an auto asset tag object with its properties such as tag name, associated organization(s), and other metadata defined by the Binalyze AIR API.
If binary data were involved (not indicated here), it would represent files or attachments related to the tags, but this operation focuses on JSON data only.
Dependencies
- Requires an active connection to the Binalyze AIR API via an API key credential configured in n8n.
- The node depends on the Binalyze AIR service being accessible and the API token having permissions to read auto asset tags.
- Pagination and search depend on the API's support for these features.
Troubleshooting
Common Issues:
- Invalid organization ID format: The organization ID must be a positive number or zero. Entering invalid values will cause validation errors.
- No results returned: Could be due to incorrect filters or no tags matching the search term.
- API authentication errors: Ensure the API key credential is valid and has sufficient permissions.
Error Messages:
"Not a valid organization ID (must be a positive number or 0 for default organization)": Fix by providing a correct numeric ID or use the list/name mode."Unknown resource": Occurs if the resource parameter is incorrectly set; ensure "autoassettags" is selected.- Network or permission errors: Check API connectivity and credentials.
Links and References
- Binalyze AIR Official Documentation — For detailed API reference and usage guidelines.
- n8n Documentation — For general information on creating and using custom nodes and credentials.