Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node updates account codes in an external system via an API. It is useful when you need to modify existing account code details programmatically within an n8n workflow, such as updating financial or organizational data linked to accounts.

Practical examples include:

  • Automatically correcting or enriching account code information based on external triggers.
  • Synchronizing updated account codes from another system into the target platform.
  • Bulk updating account codes by looping over multiple inputs.

Properties

Name Meaning
Account Id Identifier of the account whose account code you want to update.
Body JSON object representing the account code data to update, excluding autogenerated fields.

Output

The node outputs a JSON object containing the response from the API after updating the account code. This typically includes the updated account code details or confirmation of the update operation. There is no indication that binary data is handled or returned.

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.
  • Depends on the external API described in the bundled OpenAPI specification (payhawk.api.json).

Troubleshooting

  • Invalid Account Id: If the provided account identifier does not exist, the API may return a 404 error. Verify the account ID before running the node.
  • Malformed JSON in Body: Ensure the JSON body is correctly formatted and excludes autogenerated fields; otherwise, the API might reject the request.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm that the API key and base URL are correctly set in the node credentials.
  • Network Issues: Connectivity problems can cause timeouts or failed requests. Check network access to the API endpoint.

Links and References

  • Refer to the external API documentation for detailed schema and field descriptions of account codes.
  • n8n documentation on using HTTP Request nodes and JSON input formatting may help prepare the "Body" property correctly.

Discussion