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 is designed to retrieve detailed information about a specific expense from an external accounting or expense management system. It is useful in scenarios where you need to fetch and process data related to individual expenses, such as for auditing, reporting, or integration with other financial workflows. For example, you might use this node to get the details of a particular expense by its unique identifier within a given account, enabling further automation like approval workflows or expense reconciliation.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account containing the expense. This specifies the account context for the expense retrieval. |
| Expense Id | Identifier of the specific expense to retrieve. This uniquely identifies the expense record to fetch. |
Output
The node outputs a JSON object representing the detailed data of the requested expense. This typically includes fields such as expense amount, date, description, category, status, and any metadata associated with the expense. The output can be used downstream in the workflow for further processing, analysis, or storage.
If the node supports binary data (not indicated here), it would typically represent attachments or receipts related to the expense, but no binary output is evident from the provided code snippet.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to access the external expense management service.
- The node depends on an OpenAPI specification (
payhawk.api.json) that defines the available operations and endpoints. - The base URL for API requests is expected to be set via credentials configuration.
- Uses the
@devlikeapro/n8n-openapi-nodepackage for handling OpenAPI-based operations.
Troubleshooting
- Missing or invalid Account Id or Expense Id: Ensure both identifiers are correctly provided and correspond to existing records in the external system.
- Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to access expense data.
- Network or API errors: Check connectivity and API endpoint availability; ensure the base URL is correctly configured.
- Unexpected response structure: If the external API changes, the node may fail to parse the response correctly. Updating the OpenAPI spec or node version may be necessary.
Links and References
- OpenAPI Specification – Understanding the API definition format used.
- Documentation for the external expense management API (not provided here) should be consulted for detailed field descriptions and usage.