Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation retrieves detailed payment information for a specific expense within an account. It is useful in scenarios where users need to track or verify the payment status and details of individual expenses, such as auditing company spending, reconciling payments, or generating financial reports.

For example, a finance team member could use this node to fetch payment details of a particular expense to confirm whether it has been paid, the payment method used, and the date of payment.

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 whose payment details are to be fetched. This is required to pinpoint the exact expense.

Output

The node outputs JSON data containing the payment details of the specified expense. This typically includes fields such as payment status, payment date, amount paid, payment method, and any related transaction identifiers. The output structure directly reflects the payment information associated with the given expense.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential for authentication to the external service managing expenses and payments.
  • The node uses a base URL configured via credentials to connect to the external API.
  • The underlying API follows OpenAPI specifications, as indicated by usage of an OpenAPI-based properties builder.

Troubleshooting

  • Missing or invalid Account Id or Expense Id: Ensure both identifiers are provided and correctly correspond to existing records; otherwise, the API may return errors or empty results.
  • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions to access expense payment details.
  • Network or API endpoint issues: Confirm that the base URL is correct and the external service is reachable.
  • Unexpected response format: If the API changes, the node’s output structure might differ; check for updates to the node or API documentation.

Links and References

  • Refer to the external API documentation for detailed schema of expense payment details.
  • n8n documentation on using API key credentials and configuring HTTP request nodes may help in setting up authentication.

Discussion