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 perform various operations on different resources within ConnectWise Manage. Specifically, for the Configuration resource and the Update operation, this node updates an existing configuration record in ConnectWise Manage.
This is useful in scenarios where you need to programmatically modify configuration details such as type, status, associated company, or location without manually accessing the ConnectWise Manage interface. For example, automating updates to configuration records when changes occur in your asset management system or syncing configuration statuses from another tool.
Properties
| Name | Meaning |
|---|---|
| Configuration ID | The unique identifier of the configuration to update (required). |
| Additional Fields | Optional fields to update on the configuration. These include: |
- Type: One of Access, Backup, or Software. |
|
- Status: Either Active or Inactive. |
|
| - Company ID: The ID of the company associated with this configuration. | |
| - Location: The physical or logical location of the configuration. |
Output
- The output JSON contains the updated configuration object returned by the ConnectWise Manage API after the update operation.
- Each item corresponds to one input item processed.
- The structure reflects the standard ConnectWise Manage configuration resource schema, including any updated fields.
- This node does not output binary data for this operation.
Dependencies
- Requires a valid ConnectWise Manage API credential configured in n8n, which includes the API URL and authentication token.
- The node makes authenticated HTTP requests to the ConnectWise Manage REST API v3.0 endpoints.
- No additional external dependencies are required beyond the API access.
Troubleshooting
- Missing or invalid Configuration ID: The update operation requires a valid configuration ID. Ensure the ID exists and is correctly provided.
- API authentication errors: Verify that the API credentials are correct and have sufficient permissions to update configurations.
- Invalid field values: When setting additional fields like
typeorstatus, ensure the values conform to the allowed options (Access,Backup,Softwarefor type;Active,Inactivefor status). - Network or API errors: Check network connectivity and API availability. The node surfaces API error messages if the request fails.
- Empty or incomplete update data: If no additional fields are provided, the update may not change anything. Provide at least one field to update.
Links and References
- ConnectWise Manage API Documentation
- ConnectWise Manage Configuration Resource (for detailed schema and fields)