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
Purchase Orders → Update A Purchase Order
AI-generatedOverview
This node updates an existing purchase order in a system that manages purchase orders. It allows users to modify details such as the account associated with the purchase order, the supplier information, notes from the creator, and the currency used for the purchase order.
Common scenarios where this node is beneficial include:
- Correcting or updating purchase order details after creation.
- Changing the supplier or currency due to changes in business requirements.
- Adding or modifying notes for internal tracking or communication purposes.
Practical example:
- A finance team automates their workflow to update purchase orders with new supplier information received after initial entry.
- An accounting system integrates with this node to adjust purchase order currencies based on updated exchange rates or client requests.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account associated with the purchase order (required). |
| Purchase Order Id | Identifier of the purchase order to update (required). |
| Note | Text note from the creator of the purchase order, useful for additional comments. |
| Supplier | JSON object representing the supplier details related to the purchase order item. |
| Currency | Currency code for the purchase order. Options include AED, USD, EUR, GBP, JPY, and many others (full list provided). |
Output
The node outputs JSON data representing the updated purchase order. This output typically includes all relevant fields reflecting the current state of the purchase order after the update operation.
If the node supports binary data output, it would represent attachments or documents related to the purchase order, but no explicit binary output is indicated here.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to connect securely to the external purchase order management service.
- The node uses a base URL and headers preset for JSON content type and acceptance.
- Depends on an OpenAPI specification (
payhawk.api.json) for defining operations and properties.
Troubleshooting
- Missing Required Fields: Errors may occur if "Account Id" or "Purchase Order Id" are not provided. Ensure these mandatory fields are filled.
- Invalid JSON in Supplier: Since the supplier property expects JSON, malformed JSON input will cause errors. Validate JSON format before submission.
- Unsupported Currency Code: Using a currency code not listed in the options may result in rejection by the API.
- Authentication Failures: If the API key or credentials are missing or invalid, the node will fail to authenticate. Verify credential configuration.
- Network Issues: Connectivity problems to the external API endpoint can cause timeouts or failures. Check network access and base URL correctness.
Links and References
- ISO 4217 Currency Codes — Reference for currency codes supported.
- Documentation for the external purchase order API (not provided here) should be consulted for detailed field definitions and error codes.