Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation allows you to remove bank payment details from a specific expense and mark that expense as unpaid. It is useful in scenarios where a payment was recorded incorrectly or needs to be reversed, such as correcting bookkeeping errors or handling refunds. For example, if an expense was mistakenly marked as paid via bank transfer, this operation can clear the payment information and update the status accordingly.

Properties

Name Meaning
Account Id Identifier of the account associated with the expense.
Expense Id Identifier of the expense from which bank payment details will be removed and marked unpaid.

Output

The output JSON contains the updated expense data after removing the bank payment details and marking it as unpaid. This typically includes the expense's current state without any bank payment information and its updated payment status. The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing expenses.
  • The node depends on the external API endpoint that supports updating expense payment details.
  • Proper configuration of the base URL and authentication credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Account Id or Expense Id may cause the operation to fail.
    • Insufficient permissions or invalid API credentials can result in authorization errors.
    • Network connectivity problems might prevent successful API calls.
  • Error messages:

    • "Expense not found": Verify that the provided Expense Id exists and belongs to the specified Account Id.
    • "Unauthorized" or "Authentication failed": Check that the API key credential is correctly configured and has the required permissions.
    • "Invalid input": Ensure that all required properties are provided and correctly formatted.

Links and References

  • Refer to the external API documentation for managing expenses and payment details (URL depends on the service provider).
  • n8n documentation on configuring API credentials and HTTP request nodes for custom integrations.

Discussion