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 update existing service tickets. It allows users to modify various attributes of a ticket such as summary, board, type, subtype, priority, status, associated company/contact/agreement, and initial description. This is useful in scenarios where ticket details need to be corrected or updated based on new information or changes in the service process.
Practical examples include:
- Updating the priority or status of a ticket after assessing its urgency.
- Changing the assigned service board or ticket type to reflect reclassification.
- Adding or modifying the initial description to provide clearer context.
- Associating the ticket with a different company or contact if the original was incorrect.
Properties
| Name | Meaning |
|---|---|
| Ticket ID | The unique identifier of the ticket to update (required). |
| Additional Fields | A collection of optional fields to update on the ticket: |
| - Summary | The summary or title of the ticket. |
| - Board | The service board to which the ticket belongs. Options are dynamically loaded from available boards. |
| - Type | The numeric ID representing the ticket type. |
| - Subtype | The numeric ID representing the ticket subtype. |
| - Agreement ID | The numeric ID of the agreement associated with the ticket. |
| - Company ID | The numeric ID of the company linked to the ticket. |
| - Contact ID | The numeric ID of the contact person related to the ticket. |
| - Initial Description | The detailed initial description text for the ticket. |
| - Priority ID | The numeric ID indicating the priority level of the ticket. |
| - Status ID | The numeric ID indicating the current status of the ticket. |
Output
The node outputs JSON objects representing the updated ticket data returned by the ConnectWise Manage API. Each output item corresponds to an input item processed and contains the updated ticket's properties as returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the ConnectWise Manage API.
- Needs an API authentication credential configured in n8n to authorize requests.
- The node uses the base URL of the ConnectWise Manage instance provided in the credentials.
- Dynamic options for some fields (e.g., Boards) are fetched via API calls during node configuration.
Troubleshooting
- Missing or invalid Ticket ID: The update operation requires a valid Ticket ID. Ensure that the Ticket ID is correctly provided and exists in ConnectWise Manage.
- Invalid field values: Numeric IDs for fields like type, subtype, priority, status, company, contact, and agreement must correspond to existing entities in ConnectWise Manage. Invalid IDs may cause API errors.
- API authentication errors: If the API key or credentials are incorrect or expired, the node will fail to authenticate. Verify and update credentials as needed.
- Unsupported operations or resources: Attempting to use unsupported operations or resources will result in errors. Confirm that "update" operation is selected for the "ticket" resource.
- Empty or null additional fields: Fields left empty or null in the additional fields collection are ignored and not sent in the update request.
- Network or API downtime: Connectivity issues or ConnectWise Manage API outages can cause request failures. Check network connectivity and API status.
Common error messages:
"Operation 'update' is not supported for resource '...'":Indicates a mismatch between selected resource and operation."No custom fields found on ticket": When updating custom fields that do not exist on the ticket."Ticket ID parameter is missing or invalid": The required ticket identifier was not provided or invalid.