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, specifically focusing on the Configuration resource and its Get Many operation. It retrieves multiple configuration records from a ConnectWise Manage instance, supporting pagination, ordering, and filtering.
This node is beneficial when you need to programmatically fetch lists of configurations for reporting, synchronization, or automation workflows within IT service management processes. For example, you might use it to:
- Retrieve all configurations related to company assets.
- Fetch a paginated list of configurations ordered by creation date or ID.
- Integrate configuration data into dashboards or other systems.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit (boolean). |
| Limit | Maximum number of results to return if not returning all (number, minimum 1). |
| Page Number | The page number to retrieve, starting at 1 (number, minimum 1). |
| Page Size | Number of results per page, between 1 and 1000 (number). |
| Order By | Field to order results by, e.g., "id", "ID desc" (string). |
Note: The "Order By" property controls sorting of the returned configurations.
Output
The output consists of JSON objects representing configuration records retrieved from ConnectWise Manage. Each item corresponds to one configuration entity with fields as defined by the ConnectWise Manage API under the company/configurations endpoint.
The structure is an array of JSON objects, each containing configuration details such as IDs, names, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to a ConnectWise Manage instance via an API key credential configured in n8n.
- The node uses the ConnectWise Manage REST API v3.0 endpoints.
- Proper API credentials with permissions to read configurations are necessary.
- Network access to the ConnectWise Manage API URL specified in the credentials.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Requesting pages beyond available data may return empty results.
- Invalid "Order By" field values may result in API errors.
- Exceeding maximum page size (over 1000) will be rejected.
Error messages:
"Operation 'getAll' is not supported": Indicates the operation name is incorrect or unsupported for the resource."Resource 'configuration' is not supported": The resource parameter is invalid or misspelled.- API request failures often include HTTP error details; check credentials and network connectivity.
"Max number of results to return"errors occur if the limit is set below 1.
Resolutions:
- Verify API credentials and permissions.
- Use valid property values respecting constraints.
- Check network connectivity to the ConnectWise Manage API endpoint.
- Use "Return All" carefully to avoid large data loads.