Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node retrieves detailed information about a specific purchase order from an external service. 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 workflows for accounting, inventory management, or reporting.

For example, you might use this node to:

  • Automatically pull purchase order details when a new order is created in your system.
  • Validate purchase order information before processing payments or shipments.
  • Synchronize purchase order data with other business applications.

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, status, and any other relevant attributes provided by the external API.

If the node supports binary data output (not indicated here), it would represent attachments or documents related to the purchase order, but based on the provided code and properties, the output is purely JSON structured data.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the external service's API.
  • The base URL for the API must be set in the credentials configuration.
  • Depends on the external service's API endpoint that provides purchase order data.

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 to read purchase order data.
  • Network or connectivity issues: Check network access to the external API endpoint and confirm the base URL is correct.
  • 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 orders to understand the data model and available fields.
  • Consult n8n documentation on how to configure API credentials and use HTTP request nodes if customizations are needed.

Discussion