Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses 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 within an external system via an 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 incoming requests or data.
- Integrating with accounting or ERP systems to streamline purchasing.
For example, a company could use this node to create purchase orders in their financial system whenever a sales order reaches a certain stage, ensuring timely procurement of goods.
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 containing supplier information related to 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, 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 details such as purchase order ID, status, line items, supplier info, and metadata.
If the API supports binary data output (not indicated here), it would represent attachments or documents related to the purchase order.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests to the external purchase order service.
- The base URL for the API must be set in the node credentials or environment variables.
- The node depends on the external service's API being available and reachable.
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.
- Authentication errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
- Autogenerated Purchase Order Number: If you rely on auto-generation but it fails, check the account settings on the external system.
- Network issues: Confirm network connectivity to the API endpoint and that no firewall or proxy blocks the requests.
Links and References
- Refer to the external purchase order API documentation for detailed schema and examples.
- n8n documentation on creating custom nodes and handling JSON input/output.
- JSON validation tools to verify complex JSON inputs before using them in the node.