Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Purchase Orders → Get A Purchase Order

AI-generated

Overview

This node retrieves detailed information about a specific purchase order from an external system. It is useful in scenarios where you need to fetch and process data related to a particular purchase order, such as verifying order details, tracking status, or integrating purchase order data into other workflows.

For example, you might use this node to:

  • Automatically pull purchase order details when a new order ID is received.
  • Validate purchase order information before processing payments or shipments.
  • Synchronize purchase order data with accounting or inventory systems.

Properties

Name Meaning
Account Id Identifier of the account associated with the purchase order. This is required to specify which account's purchase order to retrieve.
Purchase Order Id Identifier of the specific purchase order to fetch. This uniquely identifies the purchase order within the given account.

Output

The node outputs JSON data representing the full details of the requested purchase order. This typically includes fields such as purchase order metadata, line items, amounts, dates, statuses, and any other relevant information provided by the external API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing purchase orders.
  • The base URL for the API must be configured in the node credentials or environment variables.
  • The node uses standard HTTP headers for JSON communication (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Missing or invalid Account Id or Purchase Order Id: Ensure both identifiers are correctly provided and correspond to existing records in the external system.
  • Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions.
  • Network or connectivity issues: Check network access to the API endpoint and confirm the base URL configuration.
  • Unexpected response structure: If the external API changes, the node may fail to parse the purchase order data correctly; verify API version compatibility.

Links and References

  • Refer to the external service’s official API documentation for purchase order endpoints.
  • Consult n8n documentation on configuring API credentials and HTTP request nodes for additional context.

Discussion