Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node retrieves detailed payment information for a specific expense within an account. It is useful in scenarios where you need to track or verify how an expense was paid, such as reconciling payments, auditing expenses, or integrating expense data into financial reports.

For example, a finance team could use this node to automatically fetch payment details of submitted expenses from their accounting system to ensure all payments are processed correctly.

Properties

Name Meaning
Account Id Identifier of the account containing the expense. This is required to specify which account's expense payment details to retrieve.
Expense Id Identifier of the specific expense for which payment details are requested. This is required to pinpoint the exact expense.

Output

The node outputs JSON data containing the payment details of the specified expense. The structure typically includes fields such as payment method, amount paid, date of payment, and any related transaction identifiers. No binary data output is indicated.

Dependencies

  • Requires an API key credential to authenticate requests against the external service managing expenses.
  • The node uses a base URL configured via credentials to connect to the relevant API endpoint.
  • The underlying implementation depends on an OpenAPI specification defining the available operations and properties.

Troubleshooting

  • Missing or invalid Account Id or Expense Id: Ensure both identifiers are provided and correct; otherwise, the API will likely return an error indicating the resource was not found.
  • Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to access expense payment details.
  • Network issues or incorrect base URL: Confirm that the base URL in credentials is accurate and reachable.
  • Unexpected response format: If the API changes, the node might fail to parse the response correctly; updating the node or its OpenAPI spec may be necessary.

Links and References

  • Refer to the external API documentation for detailed schema of expense payment details.
  • Consult n8n documentation on setting up API credentials and using HTTP request nodes for custom integrations.

Discussion