Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation allows users to create a new item within an existing purchase order. It is useful in scenarios where you need to add detailed line items to a purchase order, such as specifying quantities, pricing, and categorization of expenses. For example, a procurement workflow could use this node to append multiple products or services to a single purchase order dynamically.

Properties

Name Meaning
Account Id Identifier of the account associated with the purchase order.
Purchase Order Id Identifier of the purchase order to which the item will be added.
Units Unit of measurement for the purchase order item. Options: Pieces, Hours.
Expense Category JSON object describing the expense category of the purchase order item.
Expense Custom Fields JSON array defining custom fields related to the expense for the purchase order item.
Amortization JSON object containing amortization information for the purchase order item.
Description User-friendly description of the purchase order item.
Purchased Quantity Number representing how many units are being purchased.
Unit Price Price per unit of the purchase order item.

Output

The node outputs JSON data representing the created purchase order item. This typically includes all the details sent in the request along with any additional metadata or identifiers assigned by the backend system upon creation. The output does not include binary data.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to authorize requests.
  • Depends on the external Purchase Orders API endpoint to create purchase order items.
  • The base URL for the API must be set in the node credentials or environment configuration.

Troubleshooting

  • Missing Required Fields: Errors may occur if required properties like Account Id, Purchase Order Id, Description, Purchased Quantity, or Unit Price are missing or invalid. Ensure these fields are correctly filled.
  • Invalid JSON Format: Properties like Expense Category, Expense Custom Fields, and Amortization expect valid JSON strings. Malformed JSON will cause parsing errors.
  • Authentication Failures: If the API key or authentication token is incorrect or expired, the node will fail to create the item. Verify credentials and permissions.
  • API Endpoint Issues: Network problems or incorrect base URL configurations can prevent successful API calls. Confirm connectivity and correct endpoint URLs.

Links and References

  • Refer to your Purchase Orders API documentation for detailed schema and examples of purchase order item creation.
  • JSON formatting guides to ensure proper input for JSON-type properties.
  • n8n documentation on setting up API credentials and handling JSON inputs.

Discussion