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 operation lists the types of service tickets available on a specified board within ConnectWise Manage. It is useful when you want to retrieve all active ticket types associated with a particular service board, for example, to populate dropdowns, validate inputs, or automate workflows based on ticket categorization.
Practical examples:
- Automatically fetching all ticket types for a given board to create tickets with valid type selections.
- Synchronizing ticket type data from ConnectWise Manage into another system.
- Filtering or routing tickets in automation based on their type.
Properties
| Name | Meaning |
|---|---|
| Board ID | The unique identifier of the service board for which to list the ticket types. Required. |
Output
The output is an array of JSON objects, each representing a ticket type on the specified board. Each object contains at least the following fields:
id: The unique identifier of the ticket type.name: The name of the ticket type.
Example output item:
{
"id": 123,
"name": "Incident"
}
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the ConnectWise Manage API.
- The node makes HTTP GET requests to the ConnectWise Manage REST API endpoint
/service/boards/{boardId}/types. - The API base URL and authentication details must be configured in the node credentials.
Troubleshooting
- Missing Board ID: If the "Board ID" property is not provided or invalid, the node will throw an error stating that the Board ID is required.
- API Authentication Errors: If the API key or credentials are incorrect or missing, the node will fail with an authentication error.
- Empty Results: If no active ticket types exist for the specified board, the output will be an empty array.
- API Request Failures: Network issues or API downtime can cause request failures; check connectivity and API status.
- Permission Issues: Ensure the API user has permission to access service boards and ticket types.