Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Expenses → Get Expense Payments

AI-generated

Overview

This node operation, Get Expense Payments, is designed to retrieve payment details associated with a specific expense within an account. It is useful in scenarios where users need to track or audit payments made against expenses, such as financial reporting, expense reconciliation, or integration with accounting systems.

For example, a finance team could use this node to fetch all payment transactions linked to a particular expense record to verify that payments have been processed correctly or to generate detailed payment reports.

Properties

Name Meaning
Account Id Identifier of the account to which the expense belongs.
Expense Id Identifier of the specific expense for which payment details are fetched.

Output

The output will contain JSON data representing the payment information related to the specified expense. This typically includes details such as payment amounts, dates, payment methods, and statuses. The exact structure depends on the API response but generally provides comprehensive payment records tied to the expense.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication to the external service.
  • 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 endpoints defined in the bundled OpenAPI specification.

Troubleshooting

  • Missing or invalid Account Id or Expense Id: Ensure both identifiers are provided and valid; otherwise, the API call will fail or return no data.
  • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Network or connectivity issues: Check network access to the external API endpoint.
  • Unexpected API responses: Confirm that the external service is operational and that the API version matches expectations.

Links and References

  • Refer to the external service’s official API documentation for detailed information about expense payments endpoints.
  • n8n documentation on using API key credentials and configuring HTTP request nodes may be helpful for setup.

Discussion