Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation deletes a specific Goods Received Note (GRN) associated with a Purchase Order in an account. It is useful in scenarios where a previously recorded goods receipt needs to be removed, for example, if it was created by mistake or the received items were returned and the record should no longer exist.

Practical examples include:

  • Correcting inventory records by removing erroneous GRNs.
  • Managing purchase order workflows where goods receipts are updated or canceled.
  • Automating cleanup of purchase order data in integrated ERP or procurement systems.

Properties

Name Meaning
Account Id Identifier of the account under which the purchase order and goods received note exist.
Purchase Order Id Identifier of the purchase order from which the goods received note will be deleted.
Goods Received Note Id Identifier of the specific goods received note to delete.

Output

The node outputs JSON data representing the result of the deletion operation. Typically, this would include confirmation of successful deletion or details about the deleted goods received note. The exact structure depends on the API response but generally confirms that the specified GRN has been removed.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication to the external service managing purchase orders and goods received notes.
  • The node uses a base URL configured via credentials to connect to the external API.
  • The operation relies on the external service's REST API endpoint for deleting goods received notes.

Troubleshooting

  • Common issues:

    • Invalid or missing identifiers (Account Id, Purchase Order Id, Goods Received Note Id) will cause the deletion to fail.
    • Authentication errors if the API key or credentials are not set up correctly.
    • Network or connectivity issues preventing access to the external API.
  • Error messages:

    • "Not Found" or similar indicates that one or more IDs do not correspond to existing resources.
    • "Unauthorized" or "Forbidden" suggests problems with API credentials or permissions.
    • Timeout or connection errors indicate network problems.
  • Resolutions:

    • Verify all input IDs are correct and correspond to existing entities.
    • Ensure API credentials are properly configured and have sufficient permissions.
    • Check network connectivity and API endpoint availability.

Links and References

  • Refer to the external service’s API documentation for Purchase Orders and Goods Received Notes management.
  • n8n documentation on setting up API credentials and using HTTP request nodes may help configure authentication.

Discussion