Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node updates amortization records for a specified account. It is useful in financial workflows where expense amortizations need to be modified or corrected after their initial creation. For example, if an expense amortization schedule changes due to updated accounting policies or corrections, this node allows you to update the amortization details programmatically.

Properties

Name Meaning
Account Id Identifier of the account for which the amortization record will be updated.
Body JSON object representing the expense amortization data to update. This should contain the fields and values that define the new state of the amortization.

Output

The node outputs JSON data representing the updated amortization record as returned by the API. The structure corresponds to the updated amortization object, reflecting the changes made. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The node uses a base URL configured in the credentials to send requests.
  • The node depends on an OpenAPI-based client library for request construction and execution.

Troubleshooting

  • Invalid Account Id: If the provided account identifier does not exist or is malformed, the API may return an error indicating the resource was not found. Verify the account ID before running the node.
  • Malformed JSON in Body: The "Body" property expects valid JSON. Errors parsing this input will cause the node to fail. Ensure the JSON syntax is correct.
  • Authentication Errors: Missing or invalid API credentials will result in authorization failures. Confirm that the API key or token is correctly configured.
  • API Endpoint Issues: Network problems or incorrect base URL configuration can cause request failures. Check connectivity and credential settings.

Links and References

  • Refer to the external API documentation for the amortization update endpoint to understand the required and optional fields in the JSON body.
  • Consult n8n documentation on how to configure API credentials and use JSON input properties effectively.

Discussion