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 interact with service tickets and their related data. Specifically, the "Get Notes" operation under the Service Ticket resource retrieves notes associated with a given ticket. This is useful for scenarios where users want to fetch all commentary, updates, or internal notes linked to a specific support or service ticket.
Practical examples include:
- Automatically pulling all notes from a ticket to display in a dashboard or report.
- Syncing ticket notes into another system for audit or collaboration purposes.
- Triggering workflows based on the content or presence of certain notes within a ticket.
Properties
| Name | Meaning |
|---|---|
| Ticket ID | The unique identifier of the ticket whose notes you want to retrieve. |
| Return All | Boolean flag indicating whether to return all matching notes or limit the number of results returned. |
| Limit | Maximum number of notes to return if "Return All" is false (default 100, max 1000). |
| Conditions | Optional query conditions to filter the notes (e.g., filtering by status or priority). |
| Order By | Field(s) to order the results by, e.g., "priority/sort desc, ID asc". |
Output
The output consists of JSON objects representing individual notes attached to the specified ticket. Each note object contains fields as returned by the ConnectWise Manage API for ticket notes, such as note text, flags indicating note type (detail description, internal analysis, resolution), timestamps, author information, and other metadata.
If the node is used with other operations that can return binary data (like downloading documents), the binary data would be included in the binary property, but for the "Get Notes" operation, only JSON data is returned.
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 uses the base URL from the credential configuration to construct API requests.
- No additional external dependencies beyond the ConnectWise Manage API.
Troubleshooting
- Missing or invalid Ticket ID: The node requires a valid Ticket ID to fetch notes. Ensure the Ticket ID is correct and exists in ConnectWise Manage.
- API authentication errors: If credentials are incorrect or expired, API requests will fail. Verify the API key/token and permissions.
- Query condition syntax errors: The
Conditionsfield must follow ConnectWise Manage's query syntax. Invalid queries may cause API errors. - Rate limits or large data sets: When returning many notes, consider using pagination (
Return AllandLimit) to avoid timeouts or rate limiting. - Unsupported operations: Using an operation not supported for the Service Ticket resource will throw an error.
Common error messages:
"Operation 'getNotes' is not supported for resource 'ticket'": Indicates a misconfiguration or typo in operation/resource selection."No custom fields found on ticket": Occurs when trying to access custom fields that do not exist; unrelated to getNotes but possible in related operations.- API request failures with detailed error bodies logged to console for debugging.