ConnectWise Manage

Overview

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

Common scenarios where this node is beneficial include:

• Fetching contact details to enrich customer data in workflows.
• Integrating contact information into CRM or support ticket systems.
• Automating processes that require validation or lookup of contact records.

Example:
You have a workflow triggered by a new support ticket, and you want to fetch the contact details associated with the ticket to personalize communications or route the ticket appropriately.

Properties

Output

The node outputs JSON data representing the contact object retrieved from ConnectWise Manage. The structure corresponds to the contact resource schema in ConnectWise Manage and typically includes fields such as:

• contactId: Unique identifier of the contact.
• firstName, lastName: Contact's name.
• Other contact details like email, phone numbers, company association, address, etc.

The output is provided as one item per input, with the full contact record in the json property of the output item.

No binary data output is produced by this operation.

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 (siteUrl) from the credential to construct API requests.

Troubleshooting

• Error: "Operation 'get' is not supported"
  This indicates the operation or resource combination is invalid or not implemented. Verify that the Resource is set to "Contact" and Operation to "Get".

• Error: Missing Contact ID
  The Contact ID parameter is required. Ensure it is provided and correctly formatted.

• API Request Failures
  Network issues, incorrect credentials, or insufficient permissions can cause request failures. Check the API credentials and network connectivity.

• Unexpected Response Structure
  If the API response does not contain expected fields, verify the API version compatibility and that the contact exists.

• Continue On Fail Behavior
  If enabled, errors for individual items will be returned as error messages in the output instead of stopping execution.

Links and References

• ConnectWise Manage API Documentation
• n8n Documentation - HTTP Request Node (for understanding API calls)