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. It allows managing various Binalyze AIR resources such as API tokens, acquisitions, assets, cases, organizations, and more.
Specifically, the API Token - Get operation retrieves details about a specific API token from Binalyze AIR. This is useful when you want to fetch metadata or configuration related to an API token, for example, to verify its permissions or status before using it in further automation workflows.
Practical examples:
- Fetching an API token's details to audit which tokens are active.
- Retrieving token information to display in a dashboard or log.
- Using token metadata to conditionally branch workflow logic based on token properties.
Properties
| Name | Meaning |
|---|---|
| API Token | The API token to operate on. You can select it from a list of existing tokens or specify its ID manually. The ID must contain only letters, numbers, hyphens, and underscores. |
| Additional Fields | Optional extra parameters to filter or modify the request. |
| └─ Organization | Filter by organization. You can select an organization from a list, specify its numeric ID (0 for default organization), or enter its name. |
Output
The node outputs JSON data representing the details of the requested API token. This typically includes fields such as token ID, associated user or organization, creation date, expiration, scopes/permissions, and status.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate with Binalyze AIR.
- The node depends on the Binalyze AIR API being accessible and the provided API token ID being valid.
- No additional external dependencies beyond the Binalyze AIR service and its API.
Troubleshooting
- Invalid API Token ID format: If the token ID contains invalid characters, the node will reject it. Ensure the ID only contains letters, numbers, hyphens, and underscores.
- API authentication errors: If the configured API key credential is missing or invalid, the node will fail to connect. Verify the API key and permissions.
- Token not found: If the specified API token does not exist, the node may return an error or empty result. Confirm the token ID is correct.
- Organization filter issues: When filtering by organization, ensure the organization ID or name is valid. Using "0" selects the default organization.
- Network or API downtime: Connectivity issues with Binalyze AIR API will cause execution failures. Check network access and API status.
Links and References
- Binalyze AIR Official Website
- Binalyze AIR API Documentation
- n8n Documentation on Creating Custom Nodes