Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

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 correct the account associated with the expense.

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 (in JSON format).

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 update. The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the external service.
  • The base URL for the API must be configured in the node credentials.
  • The node uses standard HTTP headers for JSON communication (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Missing required properties: Ensure both "Account Id" and "Expense Id" are provided; otherwise, the update will fail.
  • Invalid JSON in External Links: The "External Links" property expects valid JSON. Malformed JSON will cause parsing errors.
  • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • API endpoint issues: Confirm the base URL is correct and the external service is reachable.
  • Error responses from API: Check error messages returned by the external system for details on why the update failed (e.g., invalid expense ID).

Links and References

  • Refer to the external system’s API documentation for detailed information about the expense update endpoint and expected payload structure.
  • n8n documentation on creating and using credentials for API authentication.

Discussion