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 organizations and their users. Specifically, the Organization - Get Users operation retrieves a paginated list of users associated with a specified organization. This is useful in scenarios where you need to automate user management workflows, audit user access within organizations, or synchronize organizational user data with other systems.
Practical examples include:
- Automatically fetching all users of an organization to update an internal directory.
- Auditing user memberships for compliance or security reviews.
- Triggering notifications or actions based on user lists within specific organizations.
Properties
| Name | Meaning |
|---|---|
| Organization | The target organization to retrieve users from. Can be selected from a list, by ID, or by name. |
| Page Number | Which page of results to return (pagination). Defaults to 1. |
| Page Size | How many user results to return per page. Defaults to 100. |
Details on "Organization" property modes:
- From List: Select an organization from a searchable dropdown list.
- By ID: Enter the numeric ID of the organization (0 represents the default organization).
- By Name: Enter the exact name of the organization.
Output
The node outputs JSON data containing the list of users retrieved for the specified organization. The structure typically includes user details such as user IDs, names, emails, roles, and other relevant metadata depending on the API response.
If the API supports pagination, the output will correspond to the requested page number and size.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Binalyze AIR API via an API key credential configured in n8n.
- The node depends on the Binalyze AIR service being accessible and the API token having permissions to read organization user data.
Troubleshooting
- Invalid Organization ID: If the entered organization ID is not a positive number or zero, the node will reject it. Ensure the ID matches the expected format.
- Empty User List: If no users are returned, verify that the organization exists and has users assigned.
- API Authentication Errors: Check that the API key credential is valid and has sufficient permissions.
- Pagination Issues: Requesting a page number beyond available pages may result in empty results; adjust page number accordingly.
- Network or Service Unavailability: Ensure connectivity to the Binalyze AIR API endpoint.
Links and References
- Binalyze AIR Official Documentation (for API details and authentication)
- n8n Documentation on Creating Custom Nodes
- Pagination concepts: REST API Pagination