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, enabling users to interact programmatically with various ConnectWise Manage resources such as tickets, companies, configurations, and more. Specifically, for the Configuration - Get operation, the node retrieves detailed information about a single configuration entity identified by its unique Configuration ID.
Common scenarios where this node is beneficial include:
- Automating retrieval of configuration details for IT asset management.
- Integrating configuration data into workflows for auditing or reporting.
- Fetching configuration information to trigger downstream processes based on configuration attributes.
For example, a user might use this node to fetch a configuration's details when a ticket is created referencing that configuration, allowing automated enrichment of ticket data or validation steps in a workflow.
Properties
| Name | Meaning |
|---|---|
| Configuration ID | The unique identifier of the configuration to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the requested configuration object from ConnectWise Manage. The structure corresponds directly to the ConnectWise Manage API response for a configuration resource, typically including fields such as:
configurationId: The unique ID of the configuration.name: The name of the configuration.- Other metadata and attributes defined in the ConnectWise Manage configuration schema.
If multiple items are processed, each output item contains the JSON representation of one configuration.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the ConnectWise Manage API.
- Requires an API authentication credential configured in n8n (an API key or token).
- The node uses the base URL provided in the credentials to construct API requests.
Troubleshooting
- Missing or invalid Configuration ID: The operation requires a valid Configuration ID. Ensure the input property is set correctly; otherwise, the node will throw an error indicating the missing or invalid parameter.
- API authentication errors: If the API credentials are incorrect or expired, the node will fail with authentication errors. Verify the API key/token and permissions.
- Unsupported operation or resource: The node validates operations and resources. Using unsupported combinations will result in clear error messages.
- Network or connectivity issues: Failures to reach the ConnectWise Manage API endpoint will cause errors. Check network access and endpoint URLs.
- API rate limits or server errors: The node surfaces API errors returned by ConnectWise Manage. Review error messages for rate limiting or server-side issues.
Links and References
- ConnectWise Manage API Documentation
- n8n Documentation on HTTP Request Node (for understanding API request handling)
- ConnectWise Manage User Defined Fields (related to custom fields mentioned in code)