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 perform various operations on different resources within ConnectWise Manage. Specifically, for the Expense resource and the Delete operation, it allows users to delete an existing expense record by its unique Expense ID.
Common scenarios where this node is beneficial include automating expense management workflows, such as removing outdated or incorrect expense entries from ConnectWise Manage without manual intervention. For example, a finance team could use this node in an automation workflow to clean up expenses that were entered erroneously or are no longer relevant.
Properties
| Name | Meaning |
|---|---|
| Expense ID | The unique identifier of the expense to delete. This is a required string input. |
Output
The output of the node after deleting an expense will be the JSON response returned by the ConnectWise Manage API for the delete request. Typically, a successful delete operation returns an empty object or confirmation status indicating the expense was deleted.
- The
jsonfield contains the API response confirming deletion. - 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 (e.g., an API key or token) to authorize requests.
- The node uses the base URL of the ConnectWise Manage instance (
siteUrl) provided by the credential configuration.
Troubleshooting
- Missing or invalid Expense ID: The node requires a valid Expense ID to delete an expense. If this is missing or incorrect, the API will return an error.
- API authentication errors: Ensure the API credentials are correctly set up and have sufficient permissions to delete expenses.
- Resource or operation not supported: If the resource or operation parameters are incorrect, the node throws an error indicating unsupported operation.
- API request failures: Network issues or API downtime can cause request failures. The node logs detailed error messages from the API response to help diagnose issues.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- ConnectWise Manage API Documentation
- n8n Documentation - HTTP Request Node (for understanding API calls)
- ConnectWise Manage Expense Resource (specific API reference for expenses)