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
This node interacts with the ConnectWise Manage API to retrieve service tickets associated with a specific contact. The "Get by Contact" operation fetches tickets linked to a given contact ID, supporting pagination and limiting the number of results returned.
Common scenarios where this node is beneficial include:
- Automatically retrieving all service tickets related to a customer or contact for reporting or processing.
- Integrating ticket data into workflows that require ticket status or history based on contact information.
- Synchronizing ticket data from ConnectWise Manage into other systems filtered by contact.
Example use case:
- A support automation workflow that, upon receiving a contact ID, fetches all open tickets for that contact to determine if there are any ongoing issues before creating a new ticket.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact whose tickets you want to retrieve. |
| Return All | Boolean flag indicating whether to return all matching tickets or limit the number fetched. |
| Limit | Maximum number of tickets to return when "Return All" is false. Value range: 1 to 1000. |
Output
The output is an array of JSON objects, each representing a service ticket associated with the specified contact. Each item contains the full ticket data as returned by the ConnectWise Manage API under the json field.
- If multiple tickets are returned, each ticket is output as a separate item.
- Pagination is handled internally when "Return All" is true, fetching up to 1000 tickets per page until all are retrieved or the limit is reached.
- No binary data is output by this operation.
Dependencies
- Requires an active connection to the ConnectWise Manage API via an API key credential configured in n8n.
- The node uses the base URL from the credential configuration to make authenticated REST API calls.
- No additional external dependencies beyond the ConnectWise Manage API and n8n's HTTP request helper.
Troubleshooting
- Missing or invalid Contact ID: The operation requires a valid contact ID. Ensure the Contact ID property is set and corresponds to an existing contact in ConnectWise Manage.
- API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions to read service tickets.
- Empty results: If no tickets are returned, confirm that the contact has associated tickets and that any conditions or filters applied (if extended) are correct.
- Limit exceeded: When "Return All" is false, the maximum number of tickets returned is capped by the "Limit" property. Increase the limit or enable "Return All" to fetch more.
- API rate limits or connectivity issues: Network problems or API throttling may cause errors. Check network connectivity and API usage quotas.
Common error messages:
"Operation 'getByContact' is not supported": Indicates an internal mismatch; ensure the operation name is correctly set."Resource 'ticket' is not supported": Means the resource parameter is incorrect or missing.- Errors from the API will be logged with details if available.
Links and References
- ConnectWise Manage API Documentation
- n8n Documentation - Creating Custom Nodes
- ConnectWise Manage Service Tickets API Reference
If you need further details about other operations or resources, feel free to ask!