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 perform various operations on service tickets and related resources. Specifically, for the Service Ticket resource and the Get Configurations operation, it retrieves configuration details associated with a specified ticket.
Typical use cases include:
- Fetching all configurations linked to a particular service ticket to understand what assets or components are involved.
- Integrating ticket configuration data into workflows for reporting, auditing, or automated processing.
- Enriching ticket information in other systems by pulling configuration details dynamically.
For example, a support automation workflow might use this node to get all configurations attached to a ticket before escalating it or sending notifications.
Properties
| Name | Meaning |
|---|---|
| Ticket ID | The unique identifier of the service ticket for which to retrieve configurations. This is a required string input. |
Output
The node outputs JSON data representing the configurations associated with the specified service ticket. The structure corresponds directly to the API response from the endpoint:
GET /service/tickets/{ticketId}/configurations
Each item in the output array (if multiple configurations exist) contains details about a configuration linked to the ticket, such as configuration IDs, names, statuses, or other metadata defined by ConnectWise Manage.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the ConnectWise Manage API.
- Needs valid API credentials configured in n8n to authenticate requests.
- The node uses the base URL from the credential's site URL property to construct API calls.
- The API version used is v4_6_release, specifically the 3.0 REST API endpoints.
Troubleshooting
- Missing or invalid Ticket ID: Since the Ticket ID is required, ensure it is provided and correctly formatted. Errors will occur if this parameter is empty or incorrect.
- API authentication errors: Verify that the API credentials are valid and have sufficient permissions to access ticket configurations.
- Unsupported operation or resource errors: If the node is misconfigured with unsupported operations or resources, it will throw errors indicating the operation/resource is not supported.
- Network or API errors: The node logs detailed error responses from the ConnectWise API. Check these logs for specific error messages like rate limits, permission denials, or malformed requests.
- Empty results: If no configurations are linked to the ticket, the output may be empty. Confirm the ticket actually has configurations in ConnectWise Manage.