Actions19
Overview
This node integrates with the Syncro RMM API to retrieve multiple tickets based on specified filters and limits. It is useful for scenarios where you need to fetch a list of support or service tickets from Syncro RMM, such as generating reports, monitoring ticket statuses, or automating workflows that depend on ticket data.
For example, you can use this node to:
- Retrieve all tickets related to a specific customer or contact.
- Search tickets by keywords or status.
- Limit the number of tickets returned for performance reasons.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching tickets or only up to a specified limit. |
| Limit | Maximum number of tickets to return when "Return All" is false. Minimum value is 1, default is 50. |
| Filters | Collection of optional filters to narrow down the tickets retrieved: |
| - Contact ID | Retrieve tickets associated with a specific contact ID. |
| - Customer ID | Retrieve tickets associated with a specific customer ID. |
| - Search Query | A text query to search tickets by any related data such as user or issue description. |
| - Status Name or ID | Filter tickets by their status, selectable from a predefined list or via expression. |
| - Ticket Search ID | Retrieve tickets matching a saved ticket search identifier. |
Output
The node outputs an array of ticket objects in the json field of the output data. Each object represents a ticket with its properties as returned by the Syncro RMM API. The exact structure depends on the API response but typically includes fields like ticket ID, status, customer/contact info, subject, description, and timestamps.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Syncro RMM API.
- Needs an API key credential configured in n8n for authentication.
- The base URL for API requests is dynamically constructed using the user's Syncro RMM subdomain.
- The node relies on internal methods to load options for ticket statuses and other dynamic dropdowns.
Troubleshooting
- Invalid API Key: If the API key is incorrect or expired, the node will fail to authenticate. Ensure the API key credential is valid and has necessary permissions.
- Empty Results: Applying overly restrictive filters may result in no tickets being returned. Try broadening filter criteria or removing some filters.
- Limit Exceeded: Setting a very high limit without enabling "Return All" might cause partial results. Use "Return All" if you want to fetch all tickets.
- API Rate Limits: Frequent calls to the Syncro RMM API may hit rate limits; consider adding delays or reducing request frequency.
Links and References
- Syncro RMM API Documentation (for detailed API endpoints and data structures)
- n8n Expressions Guide (for using expressions in property values)