AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation retrieves a list of users associated with distributors, allowing filtering and pagination through various query parameters. It is useful for scenarios where you need to fetch distributor user data based on specific criteria such as creation date ranges, email, names, or distributor identifiers. For example, it can be used to generate reports on distributor users created within a certain timeframe or to find users by their email or name patterns.

Properties

Name Meaning
Additional Query Parameters Optional filters and pagination options including:
- Created At From (Unix timestamp)
- Created At To (Unix timestamp)
- Distributor Guid (case-insensitive search pattern)
- Email (case-insensitive search pattern)
- First Name (case-insensitive search pattern)
- Last Name (case-insensitive search pattern)
- Page (JSON object specifying page number and size, defaults to 1 and max 1500)
- Transferred At From (Unix timestamp)
- Transferred At To (Unix timestamp)

Output

The output JSON contains the list of distributor users matching the specified filters. Each item in the output typically includes user details such as identifiers, names, emails, timestamps for creation and transfer, and other relevant user metadata. The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing distributor user data.
  • The node uses HTTP requests with JSON content type and expects JSON responses.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Empty results: If no users are returned, verify that the filter parameters are correct and that the date ranges or search patterns match existing data.
  • Invalid query parameter format: Ensure that numeric fields like timestamps are provided as numbers and that the page parameter is a valid JSON object.
  • API authentication errors: Confirm that the API key credential is correctly configured and has sufficient permissions.
  • Rate limiting or request failures: Check the external API's rate limits and network connectivity.

Links and References

  • Refer to the external API documentation for detailed descriptions of query parameters and response structure.
  • n8n documentation on how to configure API credentials and use collection-type input properties.

Discussion