Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node updates account codes within a specified group. It is useful in scenarios where you need to modify or correct financial or organizational account codes programmatically, such as updating accounting systems or synchronizing data between platforms. For example, if an organization restructures its chart of accounts, this node can automate the update process for multiple account codes within a group.

Properties

Name Meaning
Group Id Identifier of the account group whose account codes are to be updated (string, required).
Body JSON object representing the account code details to update, excluding autogenerated fields.

Output

The node outputs JSON data reflecting the result of the update operation on the account codes. This typically includes the updated account code information as returned by the API or service it interacts with. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to authorize requests.
  • Depends on an external API endpoint (base URL provided via credentials) that manages group account codes.
  • The node uses a JSON schema and OpenAPI-based properties builder internally, indicating reliance on a RESTful API.

Troubleshooting

  • Common issues:
    • Invalid or missing Group Id may cause the update to fail.
    • Malformed JSON in the Body property will likely result in parsing errors.
    • Authentication failures if the API key or credentials are not properly set.
  • Error messages:
    • "Invalid Group Id" or "Group not found": Verify the Group Id is correct and exists.
    • "Malformed JSON body": Ensure the Body input is valid JSON without autogenerated fields.
    • "Authentication failed": Check API credentials and permissions.

Links and References

  • No direct links available from the source code.
  • Refer to the external API documentation for the account codes service for detailed schema and usage.

Discussion