How northwestcoder/appsheet-drivemerge works
This is an AppSheet-backed documentation request app with Google Apps Script automation. Users curate Drive documents and links, create private email templates, and trigger delivery of packaged PDFs; an optional merge flow personalizes copied Docs or Sheets before delivery. The README documents the two spreadsheet-triggered scripts and the main entry point, but source excerpts were unavailable, so internal function calls between script files are not asserted.
Main entry points: main.gs Main handler · email.gs Email sender · getdocnamefromid.gs Document trigger
Components 16
App experience
- AppSheet app
- Globals settings
Content curation
- Document library
- Link library
- Request templates
Script automation
- Document trigger
getdocnamefromid.gs - Request trigger
main.gs - Main handler
main.gs - Merge parser
parser.gs - Column dictionary
columndictionary.gs
Document delivery
- Email sender
email.gs - Google Drive
- PDF attachments
Other components
- App user
- Email recipients
- AppSheet REST API
Connections 14
- App user → AppSheet app: manages content
- AppSheet app → Globals settings: updates settings
- AppSheet app → Document library: curates documents
- AppSheet app → Link library: curates links
- AppSheet app → Request templates: edits templates
- Document library → Document trigger: triggers verification
- Request templates → Request trigger: triggers sending
- Request trigger → Main handler: dispatches
- Main handler → Request templates: updates status
- Main handler → Google Drive: uses attached files
- Main handler → Email sender: sends message
- Email sender → Email recipients: delivers PDFs
- Google Drive → PDF attachments: provides content
- AppSheet REST API → Request templates: edits rows