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 updates an existing purchase order in a system that manages purchase orders. It is useful when you need to modify details of a purchase order such as the note, supplier information, or currency after it has been created. For example, if a purchase order was initially created with incorrect currency or missing notes, this node allows you to correct those details programmatically.
Typical use cases include:
- Correcting or adding additional information to a purchase order.
- Updating supplier details associated with a purchase order.
- Changing the currency of a purchase order before final processing.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the purchase order belongs. |
| Purchase Order Id | Identifier of the specific purchase order to update. |
| Note | A textual note from the creator of the purchase order, providing additional context. |
| Supplier | JSON object representing the expense category or supplier details related to the order. |
| Currency | Currency code for the purchase order. Options include standard ISO currency codes like AED, USD, EUR, GBP, etc. |
Output
The node outputs a JSON object representing the updated purchase order. This output typically includes all the fields of the purchase order after the update, reflecting any changes made through the input properties.
If the node supports binary data output (not indicated here), it would represent attachments or documents related to the purchase order, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an API key credential or similar authentication token to connect to the external purchase order management service.
- The node uses a base URL configured in credentials to send HTTP requests.
- Depends on an OpenAPI specification (
payhawk.api.json) for request structure and validation. - Uses the
@devlikeapro/n8n-openapi-nodepackage for building operations and handling API calls.
Troubleshooting
- Missing Required Fields: Ensure that both "Account Id" and "Purchase Order Id" are provided; these are mandatory to identify which purchase order to update.
- Invalid JSON in Supplier Field: The "Supplier" property expects valid JSON. Invalid JSON will cause parsing errors.
- Unsupported Currency Code: Use one of the predefined currency options. An unsupported currency code may result in API rejection.
- Authentication Errors: Verify that the API key or authentication token is correctly configured in n8n credentials.
- API Endpoint Issues: Confirm that the base URL in credentials points to the correct environment and that the API service is reachable.
Links and References
- ISO 4217 Currency Codes
- Documentation for the external purchase order API (not provided here, but typically available from the service provider)
- n8n documentation on creating custom nodes