ConnectWise Manage icon

ConnectWise Manage

Consume ConnectWise Manage API

Overview

This node interacts with the ConnectWise Manage API to list service ticket subtypes associated with a specific board and type. It is useful in scenarios where you need to dynamically retrieve and work with the hierarchical classification of service tickets, such as automating ticket categorization, reporting, or integration workflows that depend on ticket subtype information.

For example, if you have a service board representing different support areas and each board has types and subtypes for finer classification, this node operation allows you to fetch all subtypes linked to a particular type within a board. This can help in building dropdowns for subtype selection or filtering tickets by subtype in automated processes.

Properties

Name Meaning
Board ID The ID of the service board to list subtypes for. This identifies the board context.
Type ID The ID of the type within the board to list subtypes for. Subtypes returned are linked to this type.

Output

The output is an array of JSON objects, each representing a subtype associated with the specified board and type. Each object contains at least:

  • id: The unique identifier of the subtype.
  • name: The name of the subtype.

The subtype objects returned do not include the typeAssociationIds field in the final output (it is filtered out internally).

Example output item:

{
  "id": 123,
  "name": "Subtype Name"
}

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the ConnectWise Manage API.
  • Requires valid API credentials configured in n8n for authentication.
  • The node uses the base URL from the credential's site URL to construct API requests.
  • The API endpoint used is /service/boards/{boardId}/subtypes.

Troubleshooting

  • Missing Board ID or Type ID: The node will throw an error if either the Board ID or Type ID is not provided, as both are required to filter subtypes correctly.
  • No Subtypes Found: If no subtypes are associated with the given type, the output will be an empty array. Verify that the IDs are correct and that subtypes exist in ConnectWise Manage.
  • API Request Failures: Errors from the API (e.g., authentication issues, network errors) will be surfaced as node execution errors. Check your API credentials and network connectivity.
  • Invalid Operation: Using an unsupported operation or resource combination will result in an error indicating the operation is not supported.

Links and References


This summary is based solely on static analysis of the provided source code and property definitions.

Discussion