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 allows users to submit files related to expenses within an account. It is useful in scenarios where expense management requires attaching or submitting supporting documents (such as receipts or invoices) to specific expense records. For example, a finance team member can automate the process of uploading receipt images to corresponding expense entries for streamlined record-keeping and auditing.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account |
| Expense Id | Identifier of the expense to which files are submitted |
Output
The node outputs JSON data representing the result of the file submission operation. This typically includes confirmation details such as success status, metadata about the submitted files, or updated expense information. If binary data is involved (e.g., the actual files), it would be handled accordingly, but this node primarily focuses on submitting files rather than outputting them.
Dependencies
- Requires an API key credential or similar authentication token to connect to the external expense management service.
- The node depends on the external Payhawk API (or a similar service) to perform the file submission.
- Proper configuration of the base URL and authentication credentials in n8n is necessary.
Troubleshooting
- Common issues:
- Missing or invalid Account Id or Expense Id will cause the operation to fail.
- Authentication errors if the API key or credentials are not set up correctly.
- Network or connectivity problems with the external API endpoint.
- Error messages:
- "Unauthorized" or "Authentication failed": Check that the API key or credentials are correctly configured.
- "Expense not found": Verify that the provided Expense Id exists under the specified Account Id.
- "Invalid input": Ensure all required properties are provided and correctly formatted.
Links and References
- Payhawk API Documentation (example link; replace with actual)
- n8n documentation on creating custom nodes