Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

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 an 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 account.

Output

The node outputs a JSON object containing the full details of the requested purchase order. The structure 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 authentication with the external service.
  • The base URL for the API must be configured in the node credentials.
  • Depends on the external purchase order management API to fetch data.

Troubleshooting

  • Missing or invalid Account Id or Purchase Order Id: Ensure both identifiers are correctly provided and correspond to existing records.
  • Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions.
  • Network or API errors: Check connectivity and API availability; handle rate limits or downtime gracefully.
  • Unexpected response structure: Confirm that the API version matches expectations and that no breaking changes have occurred.

Links and References

  • Refer to the external purchase order API documentation for detailed schema and field descriptions.
  • Consult n8n documentation on setting up API credentials and handling HTTP request nodes for integration tips.

Discussion