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 → Create A Goods Received Note
AI-generatedOverview
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 that records the receipt of goods against a purchase order, confirming quantities and condition of items delivered. This operation is useful in inventory management and procurement workflows where tracking received goods is essential for accounting, stock updates, and supplier reconciliation.
Practical examples include:
- Automatically generating a GRN when a shipment arrives at a warehouse.
- Integrating with ERP or inventory systems to update stock levels upon receipt.
- Attaching delivery notes or scanned documents as proof of receipt.
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 are being received. |
| Note | Description or remarks about the goods received, e.g., condition, discrepancies, etc. |
| Quantities | JSON list detailing each purchase order item and the quantity actually received. |
| Document | JSON object containing details of any uploaded supporting documents related to the GRN. |
Output
The node outputs a JSON object representing the created Goods Received Note. This typically includes confirmation details such as the GRN identifier, linked purchase order, received quantities, notes, timestamps, and possibly references to attached documents. The output can be used downstream for further processing, logging, or integration with other systems.
If binary data (e.g., files or scanned documents) is included, it would represent the uploaded documents associated with the GRN, serving as proof or additional information for the receipt.
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 depends on a REST API endpoint that supports creating Goods Received Notes by accepting JSON payloads with account ID, purchase order ID, notes, quantities, and optional documents.
- Proper base URL configuration for the API endpoint is necessary in the node credentials or settings.
Troubleshooting
- Missing Required Fields: Errors may occur if
Account Id,Purchase Order Id,Note, orQuantitiesare not provided or are empty. Ensure all required fields are filled correctly. - Invalid JSON Format: The
QuantitiesandDocumentproperties expect valid JSON strings. Malformed JSON will cause parsing errors. Validate JSON syntax before input. - Authentication Failures: If the API key or authentication token is missing or invalid, the request will fail. Verify credentials and permissions.
- API Endpoint Issues: Network errors or incorrect base URL configurations can prevent successful communication with the API. Check connectivity and endpoint URLs.
- Data Mismatch: Providing quantities that do not match the purchase order items may result in validation errors from the API. Confirm that item identifiers and quantities correspond to the original purchase order.
Links and References
- Goods Received Note - Wikipedia
- Purchase Order Management Best Practices
- Refer to your API provider’s documentation for detailed schema and examples of the Goods Received Note creation endpoint.