Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation is designed to update an existing expense by removing its bank payment details and marking the expense as unpaid. It is useful in scenarios where a payment recorded against an expense needs to be reversed or corrected, such as when a payment was mistakenly applied or if the payment was canceled. For example, if an expense was marked as paid via bank transfer but the transfer failed or was refunded, this operation allows you to clear the payment information and reset the expense status accordingly.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account associated with the expense. |
| Expense Id | Identifier of the specific expense from which bank payment details will be removed. |
Output
The node outputs JSON data representing the updated expense after removal of the bank payment details and marking it as unpaid. The structure typically includes fields reflecting the expense's current state, such as its ID, status (now unpaid), and absence of bank payment information. No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing expenses.
- The node depends on a REST API endpoint that supports updating expense records.
- Proper configuration of the base URL and authentication credentials within n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Invalid or missing Account Id or Expense Id can cause the operation to fail.
- Insufficient permissions or invalid API credentials may result in authorization errors.
- Network connectivity issues can prevent communication with the external API.
Error Messages:
- "Expense not found": Verify that the provided Expense Id exists and belongs to the specified Account Id.
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly configured and has appropriate access rights.
- "Invalid input": Ensure all required properties are provided and correctly formatted.
Resolving these errors typically involves verifying input parameters, checking credential validity, and ensuring network connectivity.
Links and References
- Refer to the external expense management API documentation for details on expense updates and payment handling.
- Consult n8n documentation on setting up API credentials and configuring HTTP request nodes for similar integrations.