AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation retrieves a list of users associated with a specific collection. It is useful for scenarios where you need to manage or analyze users within a particular collection, such as fetching all users who have access to a document set, project, or resource group. For example, you might use this node to display all users in a collection on a dashboard or to automate notifications to those users.

Properties

Name Meaning
Collection Id The unique identifier of the collection whose users you want to list.
Additional Query Parameters Optional filters and controls for the query:
- Name: Filter users by their name; if a friendly name is not found, it searches by username.
- Page: JSON object specifying pagination details (page number and size).
- Sort: Sort order for the results; valid attribute is name.

Output

The output contains a JSON array of user objects belonging to the specified collection. Each user object typically includes user details such as name, username, and other relevant metadata. This allows downstream nodes or workflows to process or display user information accordingly.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication with the external service managing collections and users.
  • The node uses a base URL endpoint (not explicitly shown here) to make HTTP requests to fetch collection user data.
  • Proper configuration of the API key credential in n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid Collection Id: Ensure that the Collection Id property is provided and corresponds to an existing collection; otherwise, the request will fail or return empty results.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Invalid query parameters: When using additional query parameters like page or sort, ensure they are formatted correctly (e.g., valid JSON for page).
  • Empty results: If no users are returned, confirm that the collection actually has users and that any filters applied do not exclude all entries.

Links and References

  • Refer to the external API documentation for the collection users endpoint to understand supported query parameters and response structure.
  • n8n documentation on how to configure API key credentials and use HTTP request nodes may be helpful for setup.

Discussion