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
This node integrates with the ConnectWise Manage API to create new activities within the ConnectWise system. Activities represent tasks, calls, or meetings associated with companies or other entities managed in ConnectWise. This node is useful for automating the creation of such activities as part of workflows that track customer interactions, schedule follow-ups, or log internal tasks.
Practical examples include:
- Automatically creating a "Call" activity when a sales lead is contacted.
- Logging a "Meeting" activity after a calendar event ends.
- Creating a "Task" activity assigned to a team member for follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Name | The name/title of the activity to be created (required). |
| Additional Fields | Optional extra fields to specify more details about the activity: |
| - Type | The type of activity; options are: Call, Meeting, Task. |
| - Notes | Additional notes or description related to the activity. |
| - Company ID | The identifier of the company associated with this activity. |
Output
The node outputs JSON data representing the newly created activity object returned by the ConnectWise Manage API. This typically includes all properties of the activity such as its unique ID, name, type, notes, associated company, and timestamps.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the ConnectWise Manage API.
- The node expects the ConnectWise Manage site URL and authentication credentials to be configured in n8n.
- Network access to the ConnectWise Manage API endpoint is necessary.
Troubleshooting
- Missing Required Fields: If the "Name" property is empty or missing, the API will reject the request. Ensure all required fields are provided.
- Invalid Company ID: Providing a non-existent or incorrect company ID may cause the API to return an error. Verify the company exists in ConnectWise.
- Authentication Errors: If the API key or credentials are invalid or expired, requests will fail. Check and update credentials in n8n.
- API Endpoint Issues: Network problems or incorrect site URLs can cause connection failures. Confirm the site URL is correct and accessible.
- Error Messages: The node surfaces API error messages. Common errors include validation failures or permission denials. Review the error message details to adjust input parameters or permissions accordingly.