Actions99
- 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 ConnectWise Manage node for n8n allows you to interact with the ConnectWise Manage API. Specifically, when using the Expense resource and the Get operation, this node retrieves detailed information about a specific expense by its ID from your ConnectWise Manage account.
Common scenarios:
- Automating the retrieval of expense details for reporting or auditing.
- Integrating expense data into other workflows, such as syncing with accounting systems or generating notifications when an expense is accessed.
- Fetching expense information based on user input or as part of a larger approval process.
Practical example:
You could use this node in a workflow that, upon receiving an expense ID (perhaps from a form submission or another system), fetches the full details of that expense and then sends a summary via email or Slack.
Properties
Name | Type | Meaning |
---|---|---|
Expense ID | String | The unique identifier of the expense to retrieve. This is required. |
Output
- The output will be a single JSON object containing all available fields for the specified expense as returned by the ConnectWise Manage API.
- The structure of the output JSON depends on the fields defined in your ConnectWise Manage instance for expenses, but typically includes properties such as
expenseId
,description
,amount
,date
, etc.
Example output:
{
"expenseId": 12345,
"description": "Client dinner",
"amount": 150.00,
"date": "2024-06-01",
// ...other fields as provided by the API
}
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to a ConnectWise Manage instance with API enabled.
- API Credentials: You must configure the
connectWiseManageApi
credential in n8n, which should include:- Site URL (
siteUrl
) - Public and private API keys
- Company ID
- Site URL (
- n8n Configuration: Ensure the credentials are set up in the n8n credentials store.
Troubleshooting
Common issues:
- Invalid or missing Expense ID: If the provided Expense ID does not exist or is empty, the node will throw an error indicating the resource was not found or the parameter is missing.
- Authentication errors: Incorrect or expired API credentials will result in authentication failures.
- API connectivity issues: Network problems or incorrect site URLs can cause connection errors.
Error messages and resolutions:
"Operation 'get' is not supported"
: Ensure you have selected a valid operation for the Expense resource."Resource 'expense' is not supported"
: Double-check the resource selection; it must match exactly."Unknown error occurred during item execution"
: Review the error details in the output; check API credentials and network connectivity."The ID of the expense"
: If this field is empty or invalid, provide a correct Expense ID.