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 enables managing API tokens within the Binalyze AIR platform. Specifically, the "Get Many" operation retrieves multiple API tokens based on various filtering criteria such as active status, name, organization, and pagination options. This is useful for administrators or automation workflows that need to list, audit, or manage API tokens programmatically.
Practical examples include:
- Retrieving all active API tokens for a specific organization to audit access.
- Fetching API tokens filtered by name to identify tokens related to a particular service or user.
- Paginating through large sets of API tokens when integrating with external systems or dashboards.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional filters and pagination settings: |
- Filter By Active Status (isActive) |
Boolean flag to filter tokens by whether they are active (true) or inactive (false). |
- Filter By Name (name) |
String to filter API tokens by their name (partial or full match). |
- Organization (organizationId) |
Select an organization to filter tokens by. Options include selecting from a list, specifying by ID (positive number or 0 for default org), or by name. Using "0" retrieves tokens visible to all organizations. |
- Page Number (pageNumber) |
Number indicating which page of results to return (minimum 1). |
- Page Size (pageSize) |
Number indicating how many results to return per page (minimum 1). |
Output
The node outputs JSON data containing the retrieved API tokens matching the specified filters. Each item in the output represents an API token object with its associated properties (such as token name, status, organization, etc.). The exact structure depends on the API response but typically includes identifiers, names, statuses, and metadata about each token.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate with the Binalyze AIR API.
- The node depends on the Binalyze AIR API being accessible and the credentials having sufficient permissions to list API tokens.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common Issues:
- Authentication failures due to invalid or expired API keys.
- Permission errors if the API key lacks rights to view API tokens.
- Invalid organization IDs or names causing no results or errors.
- Pagination parameters out of range or invalid (e.g., page number less than 1).
Error Messages:
"Unknown resource: apitokens"— indicates a misconfiguration or typo in the resource parameter; ensure "API Token" resource is selected.- API authentication errors — verify the API key credential is correctly set up and valid.
- Validation errors on organization ID — ensure the organization ID is a positive number or zero for the default organization.
Resolutions:
- Double-check API credentials and permissions.
- Validate input parameters, especially organization identifiers.
- Use the built-in organization selector to avoid invalid IDs.
- Adjust pagination parameters to valid ranges.
Links and References
- Binalyze AIR API Documentation (for detailed API token management endpoints)
- n8n Documentation on Creating Custom Nodes
- General best practices for API token management and security.