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 manages API tokens within the Binalyze AIR platform, specifically supporting operations such as updating an existing API token. This is useful for automating the management of API tokens used to authenticate and authorize access to the Binalyze AIR system. For example, you can update the name, description, expiration date, or activation status of an API token programmatically as part of a workflow that manages user permissions or rotates credentials.
Properties
| Name | Meaning |
|---|---|
| API Token | The specific API token to operate on. You can select it from a list of existing tokens or specify its ID directly (must contain only letters, numbers, hyphens, and underscores). |
| Name | The new name for the API token. Must contain only alphanumeric characters, spaces, hyphens, underscores, and the at sign (@). |
| Additional Fields | Optional fields to update: • Description: A text description for the API token. • Expires At: Expiration date/time for the token. • Is Active: Boolean flag indicating whether the token is active. |
Output
The node outputs JSON data representing the updated API token object as returned by the Binalyze AIR API. This typically includes the token's ID, name, description, expiration date, active status, and other metadata. The output allows subsequent nodes in the workflow to use or log the updated token details.
No binary data output is involved.
Dependencies
- Requires an API key credential configured in n8n to authenticate with the Binalyze AIR API.
- The node depends on the Binalyze AIR service being accessible and the API token management endpoints being available.
- No additional external dependencies beyond the configured API authentication.
Troubleshooting
- Invalid API Token ID: If the provided API token ID contains invalid characters (anything other than letters, numbers, hyphens, and underscores), the node will reject it. Ensure the ID matches the required pattern.
- Name Validation Error: The token name must only include allowed characters; otherwise, validation fails. Correct the name accordingly.
- Authentication Errors: If the API key credential is missing, invalid, or lacks sufficient permissions, the node will fail to update the token. Verify the API key and its scopes.
- Expired or Inactive Tokens: Attempting to update a token that is expired or inactive may cause errors depending on API rules. Check the token status before updating.
- Network or API Errors: Connectivity issues or API downtime will cause execution failures. Retry or check service status.
Links and References
- Binalyze AIR API Documentation (for detailed API token management endpoints)
- n8n Documentation - Creating Custom Nodes