Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation deletes a specific item from a purchase order within an account. It is useful in scenarios where you need to remove an erroneous or no longer needed item from an existing purchase order, such as correcting orders before processing or updating inventory records.

Practical examples include:

  • Removing a mistakenly added product line from a purchase order.
  • Deleting discontinued items from pending purchase orders.
  • Cleaning up purchase orders before final approval or submission.

Properties

Name Meaning
Account Id Identifier of the account that owns the purchase order.
Purchase Order Id Identifier of the purchase order from which an item will be deleted.
Purchase Order Item Id Identifier of the specific purchase order item to delete from the purchase order.

Output

The output JSON typically contains the response from the API confirming the deletion of the purchase order item. This may include status information or details about the updated purchase order after the item removal.

If the node supports binary data output (not evident here), it would represent any file or media related to the operation, but this operation primarily deals with JSON data.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing purchase orders.
  • The node depends on a REST API endpoint configured via base URL and headers set in credentials.
  • Uses an OpenAPI-based client internally to interact with the purchase order service.

Troubleshooting

  • Common issues:

    • Invalid or missing identifiers (Account Id, Purchase Order Id, Purchase Order Item Id) will cause the deletion to fail.
    • Authentication errors if the API key or credentials are not properly configured.
    • Network or connectivity issues preventing access to the purchase order service.
  • Error messages:

    • "Not Found" or similar indicates the specified purchase order or item does not exist.
    • "Unauthorized" or "Forbidden" suggests invalid or insufficient permissions with the provided API key.
    • "Bad Request" may indicate malformed input parameters.
  • Resolutions:

    • Verify all IDs are correct and correspond to existing resources.
    • Ensure API credentials are valid and have necessary permissions.
    • Check network connectivity and API endpoint availability.

Links and References

  • Refer to the external purchase order service API documentation for detailed information on endpoints and request/response formats.
  • n8n documentation on creating and configuring API credential nodes.
  • General REST API troubleshooting guides.

Discussion