Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts 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 is designed to retrieve payment details associated with a specific expense within an account. It is useful in scenarios where users need to track or audit payments made against expenses, such as financial reporting, reconciliation, or expense management workflows. For example, a finance team could use this node to automatically fetch all payment records for a given expense to verify that payments have been processed correctly.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account |
| Expense Id | Identifier of the expense |
Both properties are required inputs and must be provided to specify which account and expense the payment information should be retrieved for.
Output
The node outputs JSON data containing the payment details related to the specified expense. This typically includes fields such as payment amounts, dates, payment methods, and statuses. The exact structure depends on the external API's response but generally represents a list or collection of payment records linked to the expense.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to access the external service.
- The node interacts with an external API (referred to generically here) that manages accounts, expenses, and payments.
- Proper configuration of the base URL and authentication credentials in n8n is necessary for successful API communication.
Troubleshooting
- Missing or invalid Account Id or Expense Id: Ensure both identifiers are correctly provided; otherwise, the API call will fail or return no data.
- Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to access expense payment data.
- Network or connectivity issues: Check network settings and ensure the external API endpoint is reachable from the n8n environment.
- Unexpected API responses: If the API changes or returns errors, review the API documentation and update the node configuration accordingly.
Links and References
- Refer to the external API’s official documentation for detailed information about the expense payments endpoint.
- n8n documentation on how to configure API credentials and HTTP request nodes may also be helpful.