Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation retrieves a specific item from a purchase order within an account. It is useful when you need to fetch detailed information about a particular purchase order item, such as its status, quantity, price, or other metadata. Practical scenarios include auditing purchase orders, integrating purchase order details into other workflows, or displaying item-specific data in dashboards.

Properties

Name Meaning
Account Id Identifier of the account to which the purchase order belongs.
Purchase Order Id Identifier of the purchase order containing the item.
Purchase Order Item Id Identifier of the specific purchase order item to retrieve.

Output

The output contains a JSON object representing the details of the requested purchase order item. This typically includes all relevant fields describing the item, such as product identifiers, quantities, prices, descriptions, and statuses. The node does not output binary data.

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 depends on an OpenAPI-based client library for making HTTP requests to the purchase order service.

Troubleshooting

  • Missing or invalid identifiers: Ensure that the Account Id, Purchase Order Id, and Purchase Order Item Id are correctly provided and correspond to existing entities in the system.
  • Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to access purchase order data.
  • Network issues: Check connectivity to the API endpoint and confirm that the base URL is correctly set.
  • Unexpected response structure: If the output JSON does not match expectations, verify that the API version and schema have not changed.

Links and References

  • Refer to the external purchase order API documentation for detailed information on the data model and available endpoints.
  • Consult n8n documentation on how to configure API credentials and use OpenAPI-based nodes.

Discussion