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 operation allows attaching a file to a specific Goods Received Note (GRN) within a Purchase Order in an external system. It is useful for scenarios where you need to programmatically add supporting documents, such as delivery receipts, inspection reports, or images, directly to the GRN record associated with a purchase order. For example, after receiving goods, you can automatically upload scanned delivery notes or quality check certificates to keep all related documentation organized and accessible.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account under which the purchase order exists. |
| Purchase Order Id | Identifier of the purchase order to which the goods received note belongs. |
| Goods Received Note Id | Identifier of the specific goods received note to which the file will be attached. |
Output
The node outputs JSON data representing the result of the file attachment operation. This typically includes confirmation details such as IDs of the updated records or status messages indicating success or failure. If the node supports binary data input for the file content, it would handle uploading that binary data as the attachment, but the output remains JSON confirming the operation's outcome.
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 the external API endpoint that handles file attachments to goods received notes.
- Proper configuration of base URL and headers for the API requests is necessary, usually set via credentials in n8n.
Troubleshooting
Common issues:
- Invalid or missing identifiers (Account Id, Purchase Order Id, Goods Received Note Id) will cause the operation to fail.
- Authentication errors if the API key or token is not correctly configured or expired.
- Network or permission issues preventing file upload.
Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and permissions.
- "Resource not found": Verify that the provided IDs exist and are correct.
- "File upload failed": Ensure the file data is correctly provided and the API supports the file format.
Links and References
- Refer to the external API documentation for purchase orders and goods received notes for detailed information on required parameters and file attachment capabilities.
- n8n documentation on handling binary data and configuring API credentials may help in setting up this node properly.