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 the workflow status of a specific expense within an account. It is useful for tracking the current state or progress of an expense approval or processing workflow in financial or accounting systems. For example, a user can check if an expense has been approved, rejected, or is still pending review.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account |
| Expense Id | Identifier of the expense |
Output
The output JSON contains the details of the expense's workflow status. This typically includes information such as the current state of the expense in the workflow (e.g., pending, approved, rejected), timestamps, and possibly metadata related to the approval process. The exact structure depends on the API response but will be accessible under the json output field.
No binary data output is indicated.
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 Payhawk API.
- The node depends on the Payhawk API endpoint that provides expense workflow status information.
Troubleshooting
- Missing or invalid Account Id or Expense Id: Ensure both identifiers are provided and correctly formatted; otherwise, the API call will fail.
- 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 API changes, the node might not parse the response correctly; verify API documentation for updates.
Links and References
- Payhawk API Documentation (example link, replace with actual)
- n8n OpenAPI Node integration documentation for custom nodes using OpenAPI specs