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 provides integration with Binalyze AIR, a digital forensics and incident response platform. Specifically, the "Policy" resource with the "Get Many" operation allows users to retrieve multiple security policies from Binalyze AIR. This is useful for scenarios where you want to list or filter policies based on various criteria such as name, description, enabled status, or organization visibility.
Practical examples include:
- Fetching all enabled policies for a specific organization to audit current security configurations.
- Searching policies by keywords in their descriptions to quickly find relevant rules.
- Paginating through large sets of policies to process or display them incrementally.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional filters and pagination controls to refine the list of policies returned: |
| - Filter By Description | Filter policies whose descriptions match the given string. |
| - Filter By Enabled Status | Choose between All, Enabled, or Disabled policies. |
| - Filter By Name | Filter policies by their exact or partial name. |
| - Filter By Search Term | General search term to filter policies by matching text. |
| - Organization | Select an organization to filter policies by. Use "0" to retrieve policies visible to all organizations. Can be selected from a list, by ID, or by name. |
| - Page Number | Specify which page of results to return (minimum 1). |
| - Page Size | Specify how many results to return per page (minimum 1). |
Output
The node outputs JSON data containing an array of policy objects that match the specified filters. Each policy object typically includes details such as its name, description, enabled status, associated organization, and other metadata defined by Binalyze AIR's API.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to Binalyze AIR via an API key credential configured in n8n.
- The node depends on the Binalyze AIR API being accessible and the user having appropriate permissions to read policies.
- No additional external dependencies beyond the API and credentials are required.
Troubleshooting
Common Issues:
- Incorrect or missing API authentication can cause authorization errors.
- Providing invalid organization IDs or names may result in empty results or errors.
- Requesting pages beyond available data will return empty arrays.
- Network connectivity issues can prevent successful API calls.
Error Messages:
"Unknown resource: policies"— indicates a misconfiguration or typo in the resource parameter; ensure "policies" is selected.- API errors related to authentication or permissions should be resolved by verifying the API key and user rights.
- Validation errors on input fields (e.g., organization ID format) require correcting the input according to the specified constraints.