See llms.txt for all machine-readable content.

Back to Templates

Build verified client delivery ZIPs with Google Drive, Sheets and Gmail

Quick overview

Prepare a client delivery ZIP from a Google Sheets checklist. Capture Drive file versions, export Google documents to PDF, verify the stored archive, and attach it to a Gmail draft for review.

How it works

  1. Start a manual run for the project and release set in Configure delivery.
  2. Read matching rows from the Deliverables tab. Validate required file IDs, distinct file names and optional pinned Drive versions.
  3. Read Drive metadata to check download permissions, file sizes and version numbers before downloading.
  4. Download binary files and export Google Docs, Sheets and Slides to PDF. Calculate SHA-256 hashes, then check Drive metadata again for changes made during the export.
  5. Create manifest.json and the ZIP. The manifest records the files, Drive versions, sizes and checksums.
  6. Reuse a stored package for the same source versions or upload a new ZIP. Download the stored copy, open it and verify every file against the manifest.
  7. Find the Gmail draft by its release reference. Keep an existing draft, or create one with the verified ZIP attached.

Setup

  1. Create a spreadsheet tab named Deliverables with the headers project, release, deliverable_id, file_id, archive_name and expected_version.
  2. In Configure delivery, enter the spreadsheet ID, project, release, private output folder ID and reviewEmail address. Connect Google Sheets OAuth credentials to the checklist node.
  3. Connect Google Drive OAuth credentials to the Drive nodes and Drive API HTTP Request nodes. Use an output folder with access and retention settings you control.
  4. Connect Gmail OAuth credentials to both Gmail API HTTP Request nodes. Confirm the intended draft recipient in reviewEmail.
  5. Add one checklist row for each required file. Resolve Drive shortcuts to their source file IDs, use a .pdf archive name for Google documents, and leave expected_version blank for the current version. Run manually and review the attachment, recipient and wording in Gmail before sending.

Requirements

  • Tested on n8n 2.43.8 using built-in nodes, with Google Sheets, Google Drive and Gmail OAuth credentials.

Customization

  • Use expected_version to require the current Drive version to match a version recorded in an earlier manifest.

Additional info

Run this workflow with one operator at a time for each output folder. A package supports up to 30 files, 4 MiB per downloaded or exported file, and 12 MiB total before compression.

Google PDF exports may contain different internal timestamps for the same Drive version. A repeated run reuses the verified stored export for that version. Keep the release reference in the draft subject so the draft can be found again.

Changes made during export, unsupported Google file types, duplicate archives or drafts, and archive integrity failures stop the run for review. If a draft has already been sent or deleted, another run may create a new draft. Review the Gmail recipient and attachment before sending.