Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Purchase Orders → Create A New Purchase Order

AI-generated

Overview

This node allows users to create a new purchase order within an external system via API. It is useful for automating procurement workflows, integrating purchase order creation into larger automation processes, or syncing purchase orders from other systems.

Typical use cases include:

  • Automatically generating purchase orders when certain conditions are met (e.g., inventory low).
  • Creating purchase orders programmatically based on data from other applications.
  • Centralizing purchase order management by pushing data into a single platform.

Properties

Name Meaning
Account Id Identifier of the account under which the purchase order will be created.
Note A note or comment from the creator of the purchase order.
Created By JSON object representing the creator details of the purchase order (e.g., user info).
Supplier JSON object describing the supplier associated with the purchase order.
Purchase Order Number Optional string specifying the purchase order number; if omitted, it is autogenerated.
Items JSON array listing the items included in the purchase order, each with expense category, custom fields, and amortization details.

Output

The node outputs JSON data representing the newly created purchase order as returned by the external API. This typically includes all relevant purchase order details such as ID, status, line items, supplier info, and metadata.

If binary data were involved (e.g., attachments), it would be summarized here, but this node focuses on JSON data only.

Dependencies

  • Requires an API key credential for authenticating requests to the external purchase order service.
  • The base URL for the API must be configured in the node credentials.
  • The node uses standard HTTP headers for JSON content negotiation.

Troubleshooting

  • Missing required properties: Ensure that all required fields like Account Id, Note, and Created By are provided; otherwise, the API may reject the request.
  • Invalid JSON format: Properties like Created By, Supplier, and Items expect valid JSON strings. Malformed JSON will cause parsing errors.
  • API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Autogenerated purchase order number: If you rely on auto-generation but it fails, check account settings on the external system.
  • Network or connectivity issues: Confirm that the base URL is reachable and no firewall blocks the connection.

Links and References

  • Refer to the external purchase order API documentation for detailed schema and business rules.
  • n8n documentation on creating custom nodes and handling JSON input/output.

Discussion