Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Expenses → Update Expense

AI-generated

Overview

This node updates an existing expense record in an external system. It is useful when you need to modify details of a previously created expense, such as correcting information or adding additional references. For example, you might update the expense to link it with new external documents or adjust its associated account.

Properties

Name Meaning
Account Id Identifier of the account to which the expense belongs.
Expense Id Identifier of the specific expense record that you want to update.
External Links An array of links to external system records related to the expense (e.g., URLs, IDs).

Output

The node outputs JSON data representing the updated expense record after the operation completes. This typically includes the updated fields and any metadata returned by the external system confirming the changes. The output does not include binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the external service.
  • The node uses a base URL configured in the credentials to send HTTP requests.
  • The node depends on the external system's API supporting expense updates via REST calls.

Troubleshooting

  • Missing Required Fields: If "Account Id" or "Expense Id" are not provided, the node will fail. Ensure these are set correctly.
  • Invalid JSON in External Links: The "External Links" property expects valid JSON. Malformed JSON will cause parsing errors.
  • Authentication Errors: If the API key or base URL is incorrect or missing, the node will return authentication failures.
  • Resource Not Found: If the specified expense ID does not exist, the external API may return a 404 error.
  • To resolve errors, verify all input properties, check API credentials, and confirm the expense exists in the external system.

Links and References

  • Refer to the external system’s API documentation for the "Update Expense" endpoint to understand supported fields and response structure.
  • n8n documentation on how to configure API credentials and use JSON input fields.

Discussion