Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Purchase Orders → Attach A File To A Goods Received Note

AI-generated

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 upload or link supporting documents, such as delivery receipts, inspection reports, or images, directly to the GRN record for better tracking and documentation.

Practical examples include:

  • Uploading scanned delivery notes or packing slips to confirm receipt of goods.
  • Attaching quality inspection certificates or photos to the GRN.
  • Adding any relevant files that support the purchase order fulfillment process.

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, status messages, or metadata about the attached file. The exact structure depends on the external API's response but generally confirms successful linking of the file to the specified Goods Received Note.

If binary data handling is involved (e.g., uploading the actual file content), the node would manage this internally, but no explicit binary output is indicated here.

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 the external system's API endpoints to perform the file attachment operation.
  • Proper configuration of base URL and authentication credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing identifiers (Account Id, Purchase Order Id, Goods Received Note Id) can cause failures.
    • Authentication errors if API credentials are not set or expired.
    • Network connectivity problems preventing access to the external API.
    • File size or format restrictions imposed by the external system.
  • Error messages and resolutions:

    • "Unauthorized" or "Authentication failed": Verify API credentials and permissions.
    • "Not Found" or "Invalid ID": Check that all provided IDs correspond to existing records.
    • "File upload failed": Ensure the file meets size and format requirements; check network stability.
    • Timeouts: Increase timeout settings or verify API availability.

Links and References

  • Refer to the external system’s API documentation for detailed information on the Purchase Orders and Goods Received Notes endpoints.
  • Consult n8n documentation on configuring API credentials and handling file uploads.

Discussion