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 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 by providing the relevant account and expense identifiers.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the expense belongs. |
| Expense Id | Identifier of the specific expense whose workflow status is being queried. |
Output
The output JSON contains the workflow status details of the specified expense. This typically includes fields indicating the current state of the expense in its approval or processing lifecycle. The exact structure depends on the external API response but generally provides status indicators such as "approved", "pending", "rejected", timestamps, and possibly comments or metadata related to the workflow.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authentication with the external service managing expenses.
- The node uses a base URL configured via credentials to connect to the external API.
- The operation relies on the external service's REST API endpoint that returns expense workflow statuses.
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 connectivity issues: Confirm that the base URL is reachable and the network allows outbound requests.
- Unexpected API responses: If the external service changes its API, the node might not parse the response correctly. Check for updates or contact support.
Links and References
- Refer to the external expense management system’s API documentation for detailed information about the workflow status endpoint.
- n8n documentation on creating and using API credentials.