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 integrates with Binalyze AIR to manage evidence repositories. Specifically, the "Repository - Get" operation retrieves detailed information about a single evidence repository by its identifier or name. This is useful in digital forensics and incident response workflows where you need to fetch metadata or configuration details of a specific evidence repository before performing further actions such as analysis, reporting, or exporting data.
Practical examples include:
- Fetching repository details to verify its configuration.
- Retrieving repository metadata to link it with case management systems.
- Using repository info to automate evidence collection workflows.
Properties
| Name | Meaning |
|---|---|
| Repository | The evidence repository to retrieve. You can specify it by: - Selecting from a list of repositories (searchable) - Entering the repository ID (alphanumeric, hyphens, underscores only) - Entering the repository name |
Output
The node outputs JSON data representing the retrieved repository's details. This typically includes all relevant metadata fields of the repository such as its ID, name, description, configuration settings, creation date, and other attributes defined by the Binalyze AIR API.
No binary data output is expected 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 permissions to read repository information.
Troubleshooting
- Invalid Repository ID Format: If you enter a repository ID that contains invalid characters (anything other than letters, numbers, hyphens, or underscores), the node will reject it. Ensure the ID matches the required pattern.
- Repository Not Found: If the specified repository does not exist or the user lacks permission, the node may return an error or empty result. Verify the repository exists and your credentials have sufficient access.
- API Authentication Errors: If the API key is missing, expired, or incorrect, authentication errors will occur. Check the API key credential configuration.
- Network Issues: Connectivity problems to the Binalyze AIR service will cause failures. Confirm network access and endpoint availability.