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 user resources. Specifically, the "User - Get" operation retrieves detailed information about a single user from the Binalyze AIR system. This is useful in scenarios where you need to fetch user details for auditing, reporting, or automation workflows that depend on user data.
Practical examples include:
- Retrieving user profile information by selecting a user from a list.
- Fetching user details by specifying their unique ID or username/email.
- Automating user-related processes such as notifications or access control based on user attributes.
Properties
| Name | Meaning |
|---|---|
| User | The user to retrieve. You can specify this user in one of three ways: • From List: Select a user from a searchable list. • By ID: Enter the user's unique alphanumeric ID (letters, numbers, hyphens, underscores). • By Username: Enter the username or email address of the user. |
Output
The node outputs JSON data representing the retrieved user's details. This typically includes fields such as user ID, username, email, roles, status, and other relevant user metadata as provided by the Binalyze AIR API.
If the node supports binary data output (not indicated here), it would represent user-related files or attachments, but for this operation, the output is purely JSON-based user information.
Dependencies
- Requires an active connection to Binalyze AIR via an API key credential configured in n8n.
- The node depends on the Binalyze AIR API endpoints for user management.
- Proper permissions are needed on the API key to read user information.
Troubleshooting
- Invalid User ID Format: If entering a user ID manually, ensure it only contains letters, numbers, hyphens, or underscores. Otherwise, the node will throw a validation error.
- User Not Found: If the specified user does not exist, the node may return an error or empty result. Verify the user identifier is correct.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems with the Binalyze AIR API will cause execution failures; check network and API availability.
Links and References
- Binalyze AIR Official Documentation (for API details and user resource info)
- n8n Documentation on Creating Custom Nodes