Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation "Open A Purchase Order" under the "Purchase Orders" resource is designed to interact with a purchase order system, specifically to open or activate a purchase order identified by its unique ID. It is useful in workflows where automated management of purchase orders is required, such as triggering subsequent processing steps once a purchase order is opened.

Practical examples include:

  • Automatically opening a purchase order after it has been created and approved.
  • Integrating with accounting or inventory systems to update status when a purchase order becomes active.
  • Triggering notifications or downstream processes that depend on the purchase order being open.

Properties

Name Meaning
Account Id Identifier of the account associated with the purchase order. This is required to specify which account context the purchase order belongs to.
Purchase Order Id Identifier of the specific purchase order to be opened. This uniquely identifies the purchase order within the account.

Output

The node outputs JSON data representing the result of the "open purchase order" operation. This typically includes details about the updated purchase order status and any relevant metadata returned from the API after successfully opening the purchase order.

If the node supports binary data output (not evident from the provided code), it would represent any file or document related to the purchase order, but this is not indicated here.

Dependencies

  • Requires an API key credential for authentication with the external purchase order service.
  • The base URL for the API must be configured in the node credentials or environment variables.
  • Depends on the external purchase order API endpoint that handles the "open purchase order" action.

Troubleshooting

  • Missing or invalid Account Id or Purchase Order Id: Ensure both identifiers are correctly provided and correspond to existing entities in the external system.
  • Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions.
  • API connectivity issues: Check network access and the correctness of the base URL configuration.
  • Unexpected API responses: Review the API documentation for error codes and ensure the request payload matches expected formats.

Links and References

  • Refer to the external purchase order system's API documentation for detailed information on the "open purchase order" endpoint.
  • n8n documentation on creating custom nodes and handling API requests.

Discussion