Request Tracker icon

Request Tracker

Consume Request Tracker REST2 API

Actions15

User → Get Many

AI-generated

Overview

This node interacts with the Request Tracker REST2 API to retrieve multiple user records based on specified filters and options. It is useful for scenarios where you need to fetch a list of users from a Request Tracker system, such as for reporting, user management, or integration with other systems. For example, you can filter users by username or email, limit the number of results, and sort the output.

Use Case Examples

  1. Retrieve all users whose username contains 'admin'.
  2. Get up to 100 users sorted by their name in descending order.
  3. Fetch users including all user types, not just privileged ones.

Properties

Name Meaning
Return All Whether to return all user results or only up to a given limit.
Limit Maximum number of user results to return when 'Return All' is false.
Filters Filters to narrow down users by username or email containing specific values.
Additional Options Additional options to customize the user query such as sort order, field to order by, and whether to include all users or only privileged users.
Simplify Whether to simplify the response by flattening custom fields.
Request Options Node-level request options such as batching, SSL certificate validation, proxy settings, and timeout.

Output

JSON

  • id - Unique identifier of the user.
  • Name - Username of the user.
  • EmailAddress - Email address of the user.
  • RealName - Real name of the user.
  • Other user fields - Additional user details returned by the API, possibly flattened if 'Simplify' is true.

Dependencies

  • Request Tracker REST2 API

Troubleshooting

  • Ensure the API credentials and instance URL are correctly configured to avoid authentication errors.
  • If SSL certificate validation fails, enable 'Ignore SSL Issues' option or fix the certificate issues.
  • Check the 'Limit' and 'Return All' settings to avoid unexpected number of results.
  • Use appropriate filters to avoid empty or overly large result sets.

Links

Discussion