Monitor a Google Drive folder, auto-generate dynamic cover pages, interleave them with documents, watermark, and store the final merged file back to Drive.
The AI agent reads PDFs from a Google Drive folder and generates per-document title pages with metadata. It interleaves each title page with its corresponding document, merges them into a single PDF, and stamps a blue company watermark on every page. Finally, it saves the final, branded PDF back to Google Drive.
Creates metadata-driven title pages and assembles a branded, single-file document.
List PDFs in the target Google Drive folder.
Generate metadata title pages for all documents.
Map each document to its corresponding title page.
Merge interleaved title pages and documents into one PDF.
Apply a blue company watermark to every page.
Save the final merged PDF back to Google Drive.
Two sentences of explanation. Before: 5 real pain points. After: 5 clear outcomes.
Simple 3-step flow for non-technical users.
Manual trigger starts the AI agent and lists all PDFs in the configured Google Drive folder.
Create an Autype Render JSON config with one title page per document and map each to its document.
Interleave title pages with documents, merge into a final PDF, apply the blue watermark, and save back to Drive.
A realistic scenario showing inputs, actions, and output.
A monthly reporting folder in Google Drive contains 5 PDFs. The AI agent generates 5 title pages with metadata, merges each title page with its corresponding document in the order Title1, Doc1, Title2, Doc2, Title3, Doc3, Title4, Doc4, Title5, Doc5, applies a blue watermark on all pages, and saves the final file as merged-documents-2026-04-27.pdf back to the same folder.
Roles that gain from automated, branded document packaging.
Need to assemble monthly bundles quickly with consistent branding.
Deliverables require clear per-document separation in a single file.
Archive multiple documents with metadata cover pages for auditing.
Maintain consolidated, branded documentation for records.
Provide clients with a single packaged file containing related PDFs.
Automate repetitive packaging tasks and reduce manual errors.
Tools used inside the AI agent workflow and how they are used.
Reads PDFs from a folder, downloads documents during processing, and uploads the final merged PDF back to Drive.
Renders title pages via a batch API call and provides per-document pages for merging; supports extraction and interleaving.
Common scenarios where this AI agent shines.
Common questions about setup, security, and capabilities.
Yes. This workflow relies on community nodes that require a self-hosted n8n instance. You’ll configure credentials for Google Drive and Autype inside your local or self-hosted environment. The setup steps involve installing the Autype node, obtaining an API key, and ensuring network access to Google Drive. After installation, you can import the provided workflow and connect your credentials. This keeps your data behind your own infrastructure and gives you full control over execution timing.
Autype is required for rendering and extracting the title pages used in the merge. You provide an API key for Autype on a credential within n8n so requests are authenticated securely. The credentials are stored in your self-hosted instance and are only transmitted to Autype over encrypted channels. Access to these credentials should be restricted to authorized users. You can rotate keys per your security policy.
Yes. The watermark text and styling are configurable. You can replace the default label with your company name or a confidentiality tag and adjust color, opacity, and placement. The watermark is applied to every page of the final PDF. You can update the settings in the watermark node before running the workflow.
The AI agent builds a deterministic order by numbering the documents as found in the folder at run time and pairing each with its corresponding title page. If new PDFs are added or removed between runs, the resulting merged file will reflect the current folder contents for that run. If you need stable sequencing across runs, you should run the workflow after arranging the folder contents or implement explicit sorting logic in the Build Title Pages step. Ultimately, each run produces a self-contained file based on the current folder state.
Yes. The workflow supports configuring the output folder and the final file name pattern. You can set a different Google Drive destination and adjust the merged file name, such as including a date or project code. This lets you route branded packages to separate folders for archival or client-specific delivery. Changes are made in the Drive nodes and final naming step before saving.
The current design assumes PDFs. If a file is corrupted or not a PDF, the processing will fail for that item unless you add pre-validation. You can implement a guard step to filter non-PDF or unreadable files before the loop. In practice, you should validate all inputs upfront and log any anomalies for manual review. This keeps the rest of the run consistent and predictable.
The workflow is designed for users who can configure n8n and Google Drive/Autype credentials. While no custom coding is required to run the provided workflow, you will need a basic understanding of how to install and connect community nodes in a self-hosted environment. If you’re comfortable with credential setup and importing workflows, you can deploy and run it with minimal coding. For advanced customizations, some scripting within the Code nodes may be helpful.
Monitor a Google Drive folder, auto-generate dynamic cover pages, interleave them with documents, watermark, and store the final merged file back to Drive.
