Actions109
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Websites Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Users Actions
- Activity Logs Actions
- Articles Actions
Overview
The "AvantGuard - Hudu" node for n8n allows users to interact with the Hudu API, specifically to retrieve a list of users based on various filter criteria. The "Get Users" operation under the "Users" resource enables you to search, filter, and paginate through user records in your Hudu instance. This is useful for automating user management tasks, synchronizing user data with other systems, or generating reports.
Practical examples:
- Fetch all users with a specific first or last name.
- Retrieve users belonging to a particular company (portal member company ID).
- Filter users by their email address or security level.
- Paginate through large sets of users for batch processing.
Properties
| Name | Type | Meaning |
|---|---|---|
| Additional Query Parameters | collection | A group of optional filters and pagination controls for the user query. See below for details. |
| └─ First Name | string | Filter users by their first name. |
| └─ Last Name | string | Filter users by their last name. |
| └─ Search | string | Search across both first name and last name fields. |
| └─ Portal Member Company Id | number | Filter users by company ID (applies only to portal members). |
| └─ Archived | boolean | Filter users by their archived status. |
| string | Filter users by their email address. | |
| └─ Security Level | string | Filter users by their security level (e.g., 'super_admin', 'admin', etc.). |
| └─ Page | number | Specify which page of results to retrieve (for pagination). |
| └─ Page Size | number | Number of results to return per page (for pagination). |
Output
The node outputs a JSON array where each item represents a user object as returned by the Hudu API. The structure typically includes user details such as:
{
"id": 123,
"first_name": "John",
"last_name": "Doe",
"email": "john.doe@example.com",
"security_level": "admin",
"archived": false,
// ...other user fields as defined by the Hudu API
}
- If the API supports binary data, this node does not output it for this operation; only structured JSON user data is returned.
Dependencies
- External Service: Requires access to a Hudu instance with API enabled.
- API Key/Credentials: You must configure the
avantguardHuduApicredential in n8n, including the base URL and authentication token. - n8n Configuration: Ensure that the credentials are set up in n8n's credential manager.
Troubleshooting
Invalid Credentials:
Error message: "401 Unauthorized" or similar.
Resolution: Check that your API key/token and base URL are correct in the n8n credentials.Missing Required Fields:
Error message: "400 Bad Request" or similar.
Resolution: Ensure all required parameters for your Hudu instance are provided.No Results Returned:
Possible causes: Filters are too restrictive, or there are no matching users.
Resolution: Adjust or remove some filters to broaden the search.Connection Errors:
Error message: "ENOTFOUND", "ECONNREFUSED", etc.
Resolution: Verify network connectivity and that the Hudu API endpoint is accessible from your n8n instance.