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 management of API tokens within the Binalyze AIR platform. Specifically, for the "Create API Token" operation, it allows users to create new API tokens that can be used for authenticating and authorizing access to the platform's API.
This node is beneficial in scenarios where automated workflows or integrations require programmatic access to Binalyze AIR resources. For example, a security team might use this node to generate API tokens dynamically for different services or users, controlling access scopes and expiration dates.
Practical examples include:
- Creating an API token with a specific name and optional description for a new integration.
- Assigning the token to a particular organization within Binalyze AIR.
- Setting an expiration date on the token to enforce security policies.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the API token. Must contain only alphanumeric characters, spaces, hyphens, underscores, and the at sign (@). |
| Additional Fields | Optional additional settings for the API token: |
| - Organization | The organization to which the API token belongs. Can be selected from a list, specified by ID (positive number or 0 for default), or by name. |
| - Description | An optional textual description of the API token. |
| - Expires At | An optional expiration date/time for the API token, after which it will no longer be valid. |
Output
The node outputs JSON data representing the created API token object. This typically includes details such as the token's unique identifier, name, associated organization, description, creation timestamp, and expiration date if set.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the Binalyze AIR platform.
- The node depends on the Binalyze AIR API being accessible and the user having sufficient permissions to create API tokens.
- No additional external dependencies are required beyond the configured API authentication.
Troubleshooting
- Invalid Name Error: If the "Name" property contains invalid characters, the node will reject the input. Ensure the name only includes alphanumeric characters, spaces, hyphens, underscores, and the at sign (@).
- Organization ID Validation: When specifying the organization by ID, it must be a positive number or zero (for the default organization). Providing invalid IDs will cause errors.
- Authentication Failures: If the API key credential is missing, invalid, or lacks permissions, the node will fail to create the token. Verify the API key and its permissions.
- Expiration Date Issues: Setting an expiration date in the past or in an incorrect format may cause errors. Use a valid future date/time.
- Unknown Resource Error: If the resource parameter is not set to "apitokens", the node will throw an error indicating an unknown resource.
Links and References
- Binalyze AIR API Documentation — Official API reference for managing API tokens and other resources.
- n8n Documentation — General guidance on using credentials and creating workflows with custom nodes.