Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node 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, reconciliation, or expense management workflows. For example, a finance team could use this node to automatically fetch all payment information related to a particular expense for review or integration into accounting software.

Properties

Name Meaning
Account Id Identifier of the account
Expense Id Identifier of the expense whose payments are to be retrieved

Output

The node outputs JSON data containing the payment details related to the specified expense. This typically includes structured information about each payment, such as payment amounts, dates, methods, and statuses. The exact structure depends on the API response but generally provides comprehensive payment records linked to the expense.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential for authentication to the external service (referred to generically).
  • The node interacts with an external API endpoint defined by the base URL configured in the credentials.
  • The node uses OpenAPI specifications bundled internally to define operations and properties.

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 or authentication token is valid 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 responses correctly; updating the node or API specification may be necessary.

Links and References

  • Refer to the external API documentation for detailed information on expense payments endpoints.
  • Consult n8n documentation on configuring API credentials and using custom nodes.

Discussion