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 operation allows users to create a Goods Received Note (GRN) for a specific Purchase Order within an account. A Goods Received Note is a document used in inventory and purchasing workflows to confirm the receipt of goods ordered via a purchase order. This operation is useful in scenarios where businesses need to track and verify incoming shipments against their purchase orders, ensuring that quantities received match what was ordered.
Practical examples include:
- Warehouse staff confirming delivery of items from suppliers.
- Automated inventory systems updating stock levels upon receipt of goods.
- Accounting or procurement teams maintaining accurate records of received goods for auditing and payment processing.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account under which the purchase order exists. |
| Purchase Order Id | Identifier of the purchase order for which the Goods Received Note is being created. |
| Note | Description or remarks about the goods received, providing additional context or details. |
| Quantities | JSON list detailing purchase order items and the quantities actually received. |
| Document | JSON object containing details of any uploaded documents related to the goods received (e.g., delivery notes, scanned receipts). |
Output
The node outputs a JSON object representing the newly created Goods Received Note. This output typically includes confirmation details such as identifiers, timestamps, and the data submitted (account ID, purchase order ID, note, quantities, and any attached documents). The exact structure depends on the API response but generally reflects the successful creation of the GRN.
There is no indication that this node outputs binary data.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests to the external service managing purchase orders and goods received notes.
- The node relies on a REST API endpoint (base URL configurable via credentials) to perform the creation of the Goods Received Note.
- Input properties must be correctly formatted, especially JSON fields (
quantitiesanddocument) which are parsed before sending.
Troubleshooting
- Invalid or missing required fields: Ensure all required properties (Account Id, Purchase Order Id, Note, Quantities) are provided and correctly formatted. Missing these will likely cause API errors.
- Malformed JSON in Quantities or Document: Since these fields expect JSON strings that are parsed, invalid JSON syntax will cause parsing errors before the request is sent.
- Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to create Goods Received Notes.
- API endpoint issues: Network problems or incorrect base URL configuration can prevent successful communication with the external service.
- Error messages from API: Typically indicate validation failures or permission issues; reviewing the error message and cross-checking input data usually resolves them.
Links and References
- Refer to the external API documentation for Purchase Orders and Goods Received Notes for detailed field descriptions and example payloads.
- n8n documentation on how to configure credentials and handle JSON inputs may be helpful for setup and troubleshooting.