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 List Documents operation under the Service Ticket resource retrieves documents associated with a given ticket. This is useful for scenarios where you need to programmatically access or process files linked to support tickets, such as attachments, logs, or other relevant documentation.
Practical examples include:
- Automatically fetching all documents attached to a specific ticket for archival or analysis.
- Filtering documents by certain conditions or ordering them by specific fields.
- Integrating ticket documents into other workflows like document management systems or customer portals.
Properties
| Name | Meaning |
|---|---|
| Ticket ID | The unique identifier of the ticket whose documents you want to list. |
| Return All | Whether to return all matching documents or limit the number of results. |
| Limit | Maximum number of documents to return if "Return All" is false (range 1–1000). |
| Conditions | Query conditions to filter the documents (e.g., filtering by status or other metadata). |
| Order By | Field(s) to order the results by, supporting multiple fields and sort directions (e.g., "priority/sort desc, ID asc"). |
Output
The output is an array of JSON objects representing documents associated with the specified ticket. Each object contains the document's metadata as returned by the ConnectWise Manage API. The exact structure depends on the API response but typically includes identifiers, names, types, and other document attributes.
If the Download Document special operation is used (not part of List Documents but related), the node can output binary data representing the actual file content, including metadata such as filename and MIME type.
Dependencies
- Requires a valid connection to the ConnectWise Manage API via an API key credential configured in n8n.
- The node uses the base URL from the credential configuration to make authenticated REST API calls.
- No additional external dependencies are required beyond the configured API authentication.
Troubleshooting
- Missing or invalid Ticket ID: The operation requires a valid Ticket ID; ensure this is provided and correct.
- API errors: If the API returns errors (e.g., permission denied, not found), the node will throw an error with the message from the API. Check your API credentials and permissions.
- Empty results: If no documents match the conditions or the ticket has no documents, the output will be empty.
- Limit and pagination: When "Return All" is false, the node limits results to the specified "Limit". To retrieve more, enable "Return All".
- Invalid query conditions or orderBy syntax: Ensure that the conditions and orderBy strings follow the expected format supported by ConnectWise Manage API queries.