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 operation retrieves reimbursement details for a specific user within a given account. It is useful in scenarios where you need to fetch financial or expense reimbursement information related to users, such as in accounting, payroll, or expense management workflows. For example, an HR automation workflow might use this node to pull reimbursement data for employees to generate reports or trigger payment processes.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account |
| User Id | Identifier of the user whose reimbursements are being retrieved |
Output
The output JSON contains the reimbursement details associated with the specified user and account. This typically includes structured data about reimbursement transactions, amounts, dates, statuses, and possibly related metadata. The exact structure depends on the external API response but will be accessible under the json field of the output item.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authentication with the external service.
- The node uses a base URL configured via credentials to connect to the external API.
- The node depends on an OpenAPI specification (
payhawk.api.json) that defines the available operations and their parameters.
Troubleshooting
- Missing or invalid Account Id/User Id: Ensure both identifiers are provided and correctly formatted; otherwise, the API call may fail or return no data.
- Authentication errors: Verify that the API key credential is set up correctly and has sufficient permissions.
- Network or API errors: Check connectivity and API availability; transient errors may require retries.
- Unexpected response structure: If the output does not match expectations, confirm that the API version and endpoint have not changed.
Links and References
- Refer to the external API documentation for detailed information on the reimbursement data schema and authentication requirements.
- n8n documentation on creating and using custom nodes with OpenAPI specifications.