Actions102
- Activity Actions
- Agreement Actions
- Company Actions
- Configuration Actions
- Contact Actions
- Document Actions
- Expense Actions
- Invoice Actions
- Member Actions
- Opportunity Actions
- Product Catalog Actions
- Project Actions
- Purchase Order Actions
- Schedule Actions
- Service Ticket Actions
- Time Actions
Overview
The node integrates with the ConnectWise Manage API to interact with Service Tickets, specifically supporting the "Get Many" operation for retrieving multiple service tickets. It allows users to fetch a list of tickets with flexible filtering, ordering, and pagination options.
This node is beneficial in scenarios where you need to automate ticket management workflows, generate reports on open or closed tickets, or synchronize ticket data with other systems. For example, a support team could use it to pull all high-priority tickets created within the last week, ordered by creation date, to prioritize their work.
Properties
| Name | Meaning |
|---|---|
| Order By | Field(s) to order results by, e.g., "priority/sort desc, ID asc" or "id". Determines sorting order. |
| Page Number | The page number to retrieve (starts at 1). Useful for paginated results. |
| Page Size | Number of results to return per page (minimum 1, maximum 1000). |
| Return All | Boolean flag indicating whether to return all matching results or limit the output. |
| Limit | Maximum number of results to return when not returning all (minimum 1, maximum 1000). |
| Conditions | Query conditions to filter results, e.g., "status/ID=1 and priority/ID=3". Supports complex filters. |
Output
- The output is an array of JSON objects representing service tickets.
- Each item corresponds to one ticket with its properties as returned by the ConnectWise Manage API.
- When downloading documents (not applicable here), binary data would be included, but for "Get Many" tickets, only JSON data is returned.
Dependencies
- Requires an API key credential for authenticating with the ConnectWise Manage API.
- The node uses the base URL from the credential configuration to construct API requests.
- No additional external dependencies are required beyond the ConnectWise Manage API access.
Troubleshooting
- Invalid Operation Error: If an unsupported operation is selected, the node throws an error stating the operation is not supported.
- Missing Required Parameters: For some operations, required parameters like Board ID or Type ID must be provided; otherwise, errors will occur.
- API Request Failures: Network issues or invalid credentials can cause API request failures. The node logs detailed error responses if available.
- Pagination Limits: When
Return Allis false, the node limits results to the specifiedLimit. SettingReturn Allto true fetches up to 1000 items due to API constraints. - Malformed Conditions: Incorrectly formatted query conditions may result in no data or API errors. Ensure conditions follow the expected syntax.
Links and References
This summary focuses on the "Service Ticket" resource and the "Get Many" operation, describing how to retrieve multiple tickets with filtering, ordering, and pagination using the ConnectWise Manage API through this n8n node.