Operations & Systems
Image -> PDF GDrive
This n8n workflow uses Google Drive and Google Slides (via native nodes & HTTP Requests) to convert images into a PDF. It fetches sorted PNGs from a Google Drive folder, inserts each into a new slide within a templated Google Slides presentation, then converts the presentation…
Built · ~4 hours saved per week
Image to PDF from Google Drive
Workflow Overview This workflow automates the process of collecting images from a specific Google Drive folder, assembling them into a Google Slides presentation, and exporting the final result as a single, multi-page PDF. It's designed to create documents, books, or portfolios from a series of images in a specific order, using a Google Slides file as a template to control the page dimensions (e.g., A4, US Letter, custom sizes).
Automation & Value The key value of this automation is the elimination of tedious manual work. Instead of manually creating a presentation, inserting each image one by one, resizing it to fit the page, and finally exporting to PDF, this workflow does it all in a single run. It provides a scalable and consistent method for converting a collection of images into a professional-looking PDF document, ordered chronologically by when the images were created. This is ideal for generating reports, creating lookbooks from product shots, or compiling scanned documents into one file.
Technologies Used - Google Drive: Used for storing and retrieving the source images and the final PDF. It's also used to copy the template file and manage file permissions. - Google Slides: Functions as the core engine for document assembly. The workflow uses the Google Slides API to programmatically create slides and place images. - HTTP Request Node: Used to make direct calls to the Google Slides and Google Drive APIs for advanced operations not available in the standard nodes, such as batch-updating a presentation to add/delete slides and insert images. - n8n: The orchestration platform that connects these services and executes the logic in a predefined sequence.
---
Node-by-Node Analysis
H3: Initialization and Setup 1. When clicking ‘Test workflow’: A manual trigger that starts the entire process. 2. Set Pdf File Name: This node defines a variable for the output PDF's filename. This makes it easy for a user to configure the output name without digging into more complex nodes. 3. CopyPdfTemplate (Google Drive): The workflow copies a pre-defined Google Slides file that acts as a template.
Tags: Content Management, Data Transformation, Google, Manual Trigger
Integrations: Google Drive, HTTP