ConnectWise Manage icon

ConnectWise Manage

Consume ConnectWise Manage API

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 Update operation, it allows users to update an existing expense record by specifying its ID and any fields they want to modify.

Common scenarios where this node is beneficial include automating updates to expense records in ConnectWise Manage as part of a workflow, such as adjusting amounts, changing associated companies, or updating the date or type of an expense after initial creation.

Practical example:

  • Automatically update an expense's amount and date after receiving approval from a finance system.
  • Change the company linked to an expense when a project is reassigned.

Properties

Name Meaning
Expense ID The unique identifier of the expense to update (required).
Additional Fields Optional fields to update on the expense. Can include:
- Amount The monetary amount of the expense (number).
- Company ID The ID of the company associated with the expense (string).
- Date The date of the expense in YYYY-MM-DD format (string).
- Type The type of expense; options are "Billable" or "Non-Billable".

Output

The node outputs JSON data representing the updated expense object returned from the ConnectWise Manage API. This JSON contains the current state of the expense after the update operation.

If multiple input items are processed, each output item corresponds to one input item, paired accordingly.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the ConnectWise Manage API via an API key credential configured in n8n.
  • The node uses the base URL of the ConnectWise Manage instance (siteUrl) provided in the credentials.
  • Proper permissions in ConnectWise Manage are necessary to update expense records.

Troubleshooting

  • Error: Operation 'update' is not supported for resource 'expense'
    This indicates a mismatch between the requested operation and the implemented ones. Ensure you select the correct resource and operation.

  • Missing Expense ID
    The update operation requires the Expense ID to identify which record to update. Make sure this property is set and valid.

  • API Request Failures
    Errors during the API call may be due to invalid credentials, network issues, or insufficient permissions. Check your API key configuration and network connectivity.

  • Invalid Field Values
    If the API rejects certain field values (e.g., wrong date format), verify that all additional fields conform to expected formats and types.

  • Continue On Fail Behavior
    If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output JSON.

Links and References

Discussion