Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation, Get Expense Payments, retrieves payment details associated with a specific expense within an account. It is useful for financial workflows where you need to track or reconcile payments made against expenses in an accounting or expense management system.

Practical examples:

  • Fetching all payment transactions linked to a particular expense report for auditing.
  • Integrating expense payment data into a custom dashboard or reporting tool.
  • Automating notifications or follow-ups based on payment status of expenses.

Properties

Name Meaning
Account Id Identifier of the account containing the expense. This is required to specify the scope of the query.
Expense Id Identifier of the specific expense whose payments are to be retrieved. This is required to target the exact expense.

Output

The node outputs JSON data representing the payments related to the specified expense. The structure typically includes details such as payment amounts, dates, statuses, and possibly payment method information. No binary data output is indicated.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the external expense management service.
  • The base URL for the API must be set in the node credentials configuration.
  • The node depends on the external service's REST API that manages accounts, expenses, and payments.

Troubleshooting

  • Missing or invalid Account Id or Expense Id: The node requires both identifiers to fetch payments. Ensure these are correctly provided and correspond to existing records.
  • Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions.
  • API connectivity issues: Check network connectivity and the correctness of the base URL.
  • Empty results: If no payments are returned, confirm that the expense actually has associated payments in the external system.

Links and References

  • Refer to the external expense management system’s API documentation for detailed schema of expense payments.
  • n8n documentation on configuring API credentials and HTTP request nodes may help in setting up authentication.

Discussion