NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Ticketing → Get All User And Contacts

AI-generated

Overview

This node operation "Get All User And Contacts" under the "Ticketing" resource fetches a paginated list of users and contacts from the NinjaOne API. It allows filtering by user type (Technician, End User, or Contact), searching by name or email, and supports pagination through page size and anchor ID parameters.

Common scenarios where this node is useful include:

  • Retrieving all technicians or end users for reporting or synchronization with other systems.
  • Searching for specific users or contacts by partial names or emails.
  • Paginating through large user/contact lists to process them in batches.

Practical example:

  • An IT service management workflow that needs to pull all technician users to assign tickets automatically.
  • A customer support automation that fetches all contacts related to a client organization for personalized communication.

Properties

Name Meaning
Page Size Limit number of records returned per page (number).
Anchor Natural Id Last user identifier from the previous page, used for pagination (number).
Search Criteria Text to search users by first name, last name, or email address (string).
User Type Type of user to retrieve; options: TECHNICIAN, END USER, CONTACT.
Client Id Organization identifier to filter users/contacts by client (number).

Output

The output is an array of JSON objects representing users or contacts retrieved from the NinjaOne API. Each item contains the full user/contact data as returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token configured via OAuth2 credentials for the NinjaOne API.
  • The node uses the NinjaOne REST API endpoints to fetch user/contact data.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Empty results: Ensure the Client Id and User Type filters are set correctly. If searching, verify the Search Criteria matches existing user data.
  • Pagination issues: Use the Anchor Natural Id from the last fetched record to continue paging. Incorrect values may cause repeated or missing data.
  • Authentication errors: Confirm the API key or OAuth2 token is valid and has sufficient permissions to access user/contact data.
  • API request failures: Network issues or API downtime can cause errors. Check connectivity and NinjaOne service status.
  • Missing binary data error: Not applicable here since this operation does not handle binary data.

Links and References

Discussion