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 → Delete A Goods Received Note
AI-generatedOverview
This node operation deletes a specific Goods Received Note (GRN) associated with a Purchase Order in an account. It is useful in scenarios where a previously recorded goods receipt needs to be removed, for example, if it was created by mistake or the received items were returned and the record should no longer exist.
Practical examples include:
- Correcting inventory records by removing erroneous GRNs.
- Managing purchase order workflows where goods receipts are updated or canceled.
- Automating cleanup of purchase order data in integrated ERP or procurement systems.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account under which the purchase order and goods received note exist. |
| Purchase Order Id | Identifier of the purchase order from which the goods received note will be deleted. |
| Goods Received Note Id | Identifier of the specific goods received note to delete. |
Output
The output JSON contains the response from the API after attempting to delete the specified Goods Received Note. Typically, this would confirm successful deletion or provide error details if the operation failed.
If the node supports binary data output, it is not indicated here; thus, the output is expected to be purely JSON-based.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing purchase orders and goods received notes.
- The node uses a base URL configured in the credentials to connect to the API endpoint.
- No additional external dependencies are indicated beyond the API connection.
Troubleshooting
Common issues:
- Invalid or missing identifiers (Account Id, Purchase Order Id, Goods Received Note Id) will cause the deletion to fail.
- Insufficient permissions or invalid API credentials can result in authorization errors.
- Network connectivity problems may prevent the node from reaching the API.
Error messages and resolutions:
- "Not Found" or similar: Verify that all IDs are correct and correspond to existing resources.
- "Unauthorized" or "Forbidden": Check that the API key credential is valid and has sufficient permissions.
- Timeouts or network errors: Ensure stable internet connection and correct API base URL configuration.
Links and References
- Refer to the external API documentation for Purchase Orders and Goods Received Notes management for detailed information on required parameters and response formats.
- n8n documentation on creating and configuring API credentials for secure authentication.