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 integrates with Binalyze AIR to manage user data within organizations. Specifically, the "User" resource with the "Get Many" operation allows retrieving multiple users filtered by organization and other optional criteria. This is useful for workflows that need to list or process users in bulk, such as auditing user roles, syncing user lists with other systems, or generating reports on organizational user assignments.
Practical examples:
- Fetch all users belonging to a specific organization to synchronize them with an external directory.
- Retrieve users not assigned to any organization for cleanup or reassignment.
- Paginate through large user lists to process them in batches.
Properties
| Name | Meaning |
|---|---|
| Organization | The organization to filter users by. Can be specified by numeric ID (use 0 for all organizations) or by name. |
| Include Users Not in Organization | Whether to include users who are not assigned to any organization (boolean). |
| Page Number | Which page of results to return (pagination, minimum 1). |
| Page Size | How many results to return per page (pagination, minimum 1). |
| Filter By Roles | Filter users by their roles; provide a comma-separated list of role names. |
Output
The node outputs JSON data containing the list of users matching the specified filters. Each user object typically includes user details such as identifiers, names, roles, and organization membership status. The output structure aligns with the API response from Binalyze AIR's user listing endpoint.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Binalyze AIR service.
- The node depends on the Binalyze AIR API being accessible and properly configured.
- Pagination parameters allow handling large datasets efficiently.
Troubleshooting
- Invalid Organization ID: If the organization ID is not numeric, the node will reject it due to regex validation. Ensure the ID is a number or use the name mode.
- Empty Results: If no users are returned, verify the organization filter and role filters are correct and that users exist matching those criteria.
- API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to list users.
- Pagination Issues: Using page numbers or sizes outside allowed ranges may cause errors or empty responses. Use minimum values as specified.
Links and References
- Binalyze AIR API Documentation (for detailed user resource API)
- n8n Documentation on Creating Custom Nodes