Overview
This node allows users to search for tickets within the EnlightenedMSP system using a variety of filters and sorting options. It is useful in scenarios where you need to retrieve specific tickets based on criteria such as status, priority, assigned resource, queue, date ranges, or text search. For example, you could use this node to find all high-priority tickets assigned to a particular technician that were created within the last month, or to list tickets containing certain keywords in their title or description.
Properties
| Name | Meaning |
|---|---|
| Search Text | Text string to filter tickets by matching content |
| Status | Filter tickets by status with operations: Equals, Not Equals (numeric status values) |
| Priority | Filter tickets by numeric priority value |
| Assigned Resource ID | Filter tickets assigned to a specific resource by numeric ID |
| Queue ID | Filter tickets belonging to a specific queue by numeric ID |
| Due Date Range | Filter tickets with due dates between specified From and To datetime values |
| Created Date Range | Filter tickets created between specified From and To datetime values |
| Completed Date Range | Filter tickets completed between specified From and To datetime values |
| Include Archived | Boolean flag to include archived tickets in the results |
| Sort By | Field to sort results by; options: Ticket Number, Due Date, Created Date, Completed Date, Priority, Status |
| Sort Order | Sort order direction; options: Ascending, Descending |
| Page | Page number for paginated results |
| Limit | Number of results per page |
| Data Selection | Multiline string specifying which fields to return in the response. Defaults to a set of common ticket fields |
| Title | Filter tickets by title with operations: Equals, Not Equals, Contains, Not Contains |
Output
The node outputs two streams:
Main output: An array of objects each containing:
tickets: Array of ticket objects matching the query, each including the requested fields.totalCount: Total number of tickets matching the search criteria.page: Current page number of the results.limit: Number of tickets returned per page.
AI Tool output: This output is defined but not detailed in the code snippet; presumably used for AI-related processing or integration.
The ticket objects contain fields such as id, title, status, ticketNumber, description, priority, dueDateTime, createDate, completedDate, assignedResourceID, queueID, and resolution by default, or any custom selection specified in the "Data Selection" property.
No binary data output is indicated.
Dependencies
- Requires an API key credential for accessing the EnlightenedMSP GraphQL endpoint.
- The node uses a GraphQL client base class to execute queries against the EnlightenedMSP API.
- Proper configuration of the API endpoint and authentication credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect date formats in date range filters may lead to errors or no results.
- Using unsupported field names in the "Data Selection" property might result in incomplete or failed queries.
- Pagination parameters (page and limit) should be positive integers; invalid values may cause unexpected behavior.
Error messages:
- Errors from the API are caught and returned as JSON with an
errormessage if "Continue On Fail" is enabled. - Typical error messages relate to network issues, authentication failures, or malformed queries.
- Errors from the API are caught and returned as JSON with an
Resolution tips:
- Verify API credentials and permissions.
- Ensure date inputs are valid ISO 8601 strings.
- Use default or documented field names in "Data Selection".
- Adjust pagination parameters within reasonable bounds.
Links and References
- EnlightenedMSP API Documentation (primary documentation link provided in node metadata)