ConnectWise Manage

Overview

This node integrates with the ConnectWise Manage API to perform various operations on different resources within ConnectWise Manage. Specifically, for the Activity resource and the Get operation, it retrieves detailed information about a single activity by its unique ID.

Common scenarios where this node is beneficial include:

• Fetching details of a specific activity record in ConnectWise Manage for reporting or processing.
• Integrating activity data into workflows that require up-to-date information from ConnectWise Manage.
• Automating retrieval of activity metadata to trigger subsequent actions based on activity status or attributes.

Practical example:

• A workflow that triggers when an activity ID is received and uses this node to fetch all details about that activity, then sends a notification or updates another system accordingly.

Properties

Output

The node outputs JSON data representing the full details of the requested activity as returned by the ConnectWise Manage API. The structure corresponds directly to the activity object in ConnectWise Manage, including all standard fields and any custom fields associated with that activity.

No binary data output is produced for this operation.

Example output JSON (simplified):

{
  "activityId": 12345,
  "name": "Sample Activity",
  "description": "Details about the activity",
  "status": "Open",
  "startDate": "2024-01-01T12:00:00Z",
  ...
}

Dependencies

• Requires an active connection to the ConnectWise Manage API.
• Needs an API authentication credential configured in n8n to authorize requests.
• The node uses the base URL of the ConnectWise Manage instance provided in the credentials.
• No additional external dependencies beyond the ConnectWise Manage API.

Troubleshooting

• Missing or invalid Activity ID: The node requires a valid activity ID. If omitted or incorrect, the API will return an error. Ensure the Activity ID is correct and exists in ConnectWise Manage.
• API authentication errors: If the API key or credentials are invalid or expired, the node will fail to authenticate. Verify the API credentials in n8n settings.
• Resource not supported error: If the resource parameter is incorrectly set or unsupported, the node throws an error indicating the resource is not supported.
• Operation not supported error: If the operation parameter is invalid or not implemented for the resource, an error is thrown.
• API request failures: Network issues or API downtime can cause request failures. Check connectivity and API status.
• Error messages typically include HTTP response details from ConnectWise Manage. Review these messages for clues on permission issues, missing parameters, or malformed requests.

To resolve errors:

• Double-check input parameters.
• Confirm API credentials and permissions.
• Review API documentation for required fields and endpoint availability.

Links and References

• ConnectWise Manage API Documentation
• ConnectWise Manage Activities API Reference
• n8n Documentation on Creating Custom Nodes