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 "Get Lists" operation for the "Lists" resource retrieves a collection of lists from an external service (presumably Hudu, via AvantGuard integration). This node is useful when you need to fetch and filter lists based on specific criteria such as partial or exact name matches. Common scenarios include synchronizing list data with other systems, displaying available lists to users, or automating workflows that depend on list information.
Practical examples:
- Fetching all available lists to populate a dropdown in another workflow.
- Searching for lists by a partial name to find relevant entries.
- Filtering lists to retrieve only those with an exact name match.
Properties
| Name | Type | Meaning |
|---|---|---|
| Additional Query Parameters | Collection | Optional parameters to refine your search. Contains: |
| - Query | String | Search lists by name using a partial match. |
| - Name | String | Filter results to only include lists with an exact name match. |
Output
The output will be a JSON array where each item represents a list object retrieved from the external service. The structure of each list object depends on the API's response, but typically includes fields such as list ID, name, and other metadata.
Example output:
[
{
"id": 123,
"name": "Sample List",
"created_at": "2023-01-01T12:00:00Z",
"updated_at": "2023-01-02T12:00:00Z"
// ...other fields
}
]
Note: The actual fields may vary depending on the external API.
Dependencies
- External Service: Requires access to the Hudu API via AvantGuard.
- API Credentials: You must configure the
avantguardHuduApicredential in n8n, which should include the base URL and authentication details. - n8n Configuration: Ensure the credentials are set up in your n8n instance under the appropriate name.
Troubleshooting
Missing Credentials:
Error: "No credentials found for 'avantguardHuduApi'."
Resolution: Make sure you have created and selected the correct credentials in the node settings.Invalid Base URL:
Error: "Request failed with status code 404/401."
Resolution: Verify that the base URL in your credentials is correct and points to your Hudu instance.Empty Results:
Issue: No lists returned.
Resolution: Check your query parameters; try removing filters to broaden the search.API Rate Limits or Permissions:
Error: "403 Forbidden" or similar.
Resolution: Ensure your API user has permission to access lists and you are not exceeding rate limits.
Links and References
- n8n Documentation
- Hudu API Documentation (if available)
- AvantGuard n8n OpenAPI Node