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 integrates with the ConnectWise Manage API to create service tickets. It allows users to submit new tickets into their ConnectWise Manage system, specifying a summary and various optional details such as board, type, subtype, priority, status, and associations with companies, contacts, or agreements.
Common scenarios where this node is beneficial include:
- Automating ticket creation from external systems or forms.
- Integrating customer support workflows by programmatically logging issues.
- Creating tickets based on events or alerts in other software tools.
For example, when a customer submits a support request via a web form, this node can automatically create a corresponding service ticket in ConnectWise Manage with the provided summary and additional metadata.
Properties
| Name | Meaning |
|---|---|
| Summary | The main summary or title of the service ticket. This is a required field. |
| Additional Fields | A collection of optional fields to provide more details about the ticket: |
| - Summary | An optional override or additional summary text for the ticket. |
| - Board | The service board under which the ticket should be categorized. Options are dynamically loaded. |
| - Type | The numeric ID representing the ticket type. |
| - Subtype | The numeric ID representing the ticket subtype. |
| - Agreement ID | Numeric ID of an agreement to associate with the ticket. |
| - Company ID | Numeric ID of the company related to the ticket. |
| - Contact ID | Numeric ID of the contact person associated with the ticket. |
| - Initial Description | A detailed initial description of the issue or request. |
| - Priority ID | Numeric ID indicating the priority level of the ticket. |
| - Status ID | Numeric ID indicating the current status of the ticket. |
Output
The node outputs JSON objects representing the created service tickets as returned by the ConnectWise Manage API. Each output item corresponds to one created ticket and includes all standard ticket fields as per the API response.
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 (an API key or token).
- The node dynamically loads options for boards, types, and subtypes by querying the ConnectWise Manage API.
- The base URL for the API is taken from the configured credentials.
Troubleshooting
- Missing Required Fields: If the "Summary" field is empty or missing, the node will throw an error because it is mandatory for ticket creation.
- Invalid Board/Type/Subtype IDs: Selecting invalid or inactive board/type/subtype IDs may cause API errors. Ensure these are valid and active by using the dynamic option loaders.
- API Authentication Errors: If the API credentials are incorrect or expired, requests will fail. Verify that the API key/token is valid and has sufficient permissions.
- Network Issues: Connectivity problems to the ConnectWise Manage API endpoint will result in request failures.
- Unexpected API Responses: If the API returns unexpected data or errors, check the API version compatibility and review the error message logged by the node.