ConnectWise Manage

Overview

The node integrates with the ConnectWise Manage API to perform operations on various resources, including activities. Specifically, for the Activity resource and the Search operation, it allows users to search for activities based on a custom search query string. This is useful in scenarios where you want to filter activities dynamically using conditions expressed in the ConnectWise Manage query language.

Typical use cases include:

• Retrieving activities that match specific criteria such as date ranges, status, or related entities.
• Automating workflows that require fetching filtered activity data from ConnectWise Manage.
• Integrating activity search results into other systems or processes within an automation pipeline.

For example, you might search for all activities assigned to a particular user or all activities created after a certain date.

Properties

Note: The "Order By" property supports ordering the results by any valid field in ConnectWise Manage, optionally with direction (e.g., "ID desc").

Output

The node outputs an array of JSON objects, each representing an activity matching the search criteria. Each item contains the full activity data as returned by the ConnectWise Manage API under the json key.

Example output structure (simplified):

[
  {
    "json": {
      "activityId": 123,
      "name": "Sample Activity",
      "description": "Details about the activity",
      "dateCreated": "2024-01-01T12:00:00Z",
      ...
    }
  },
  ...
]

No binary data is produced by this operation.

Dependencies

• Requires a valid ConnectWise Manage API credential configured in n8n with appropriate permissions.
• The node makes authenticated HTTP requests to the ConnectWise Manage REST API endpoint specified in the credentials.
• The API version used is v3.0 under the /v4_6_release/apis/3.0 path.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials will cause authentication failures.
  • Malformed or unsupported search queries may result in API errors.
  • If the "Order By" field is invalid or misspelled, the API may return an error or unexpected results.
  • Network connectivity issues can prevent successful API calls.

• Error messages:

  • "Operation 'search' is not supported for resource 'activity'": Indicates a mismatch in resource or operation parameters.
  • API request failures typically include error details from ConnectWise Manage; check the error message for specifics.
  • "No custom fields found on ticket" or similar errors are unrelated to the activity search but may appear if other operations are misconfigured.

• Resolution tips:

  • Verify API credentials and permissions.
  • Ensure the search query syntax matches ConnectWise Manage's expected format.
  • Use valid field names for ordering.
  • Enable debug logging in n8n to see detailed request and response information.

Links and References

• ConnectWise Manage API Documentation
• ConnectWise Manage API Query Language Guide
• n8n documentation on Creating Custom Nodes