Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node allows users to create a new purchase order in an external system via an API. It is useful for automating procurement workflows, integrating purchase order creation into larger automation pipelines, 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.
- Streamlining the purchasing process by eliminating manual entry.
For example, a company could use this node to create purchase orders directly from their ERP system whenever a new supplier contract is signed.
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, including expense categories and custom fields. |
Output
The node outputs JSON data representing the newly created purchase order as returned by the API. This typically includes all details of the purchase order such as its ID, status, line items, supplier information, and metadata.
If the API supports binary data related to purchase orders (e.g., attached documents), the node would handle that accordingly, but no explicit binary output handling is indicated here.
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 depends on the external purchase order API being available and accessible.
Troubleshooting
- Invalid or missing required properties: Ensure all required fields like Account Id, Note, and Created By are provided and correctly formatted.
- JSON parsing errors: The
Created By,Supplier, andItemsfields expect valid JSON strings. Invalid JSON will cause errors. - Authentication failures: Verify that the API key credential is correctly set up and has sufficient permissions.
- API connectivity issues: Check network access and API endpoint availability.
- Autogenerated purchase order number conflicts: If you provide a purchase order number manually, ensure it does not conflict with existing numbers.
Links and References
- Refer to the external purchase order API documentation for detailed schema and field descriptions.
- n8n documentation on creating custom nodes and using JSON input properties.