+2
Convert PDF to HTML using PDF.co and Google Drive
Published 9 hours ago
Created by
WeblineIndia
Categories
Template description
This n8n workflow automates the process of converting a newly stored PDF file from Google Drive into an HTML file and saving it back to Google Drive. The workflow is triggered whenever a new PDF is uploaded to a specific folder, ensuring seamless conversion and storage without any manual intervention.
This workflow provides an efficient, automated solution for converting PDFs to HTML, eliminating the need for manual file handling and ensuring a smooth document transformation process. It is particularly useful for scenarios where PDFs need to be dynamically converted and stored in an organised manner for web usage, archiving, or further processing.
Prerequisites :
Before setting up this workflow, ensure the following:
- PDF.co API Key: Sign up at PDF.co and obtain an API key for PDF to HTML conversion.
- Proper Authentication: Ensure authentication is configured for Google Drive in n8n.
Customisation Options :
- Modify the API request to convert PDFs to other formats like Text, CSV, or XML.
- Extend the IF Node to reject files based on size or other properties.
- Send a notification once the conversion is complete using an Email or Telegram Node.
Steps :
Step 1: Google Drive Trigger Node (Watch for New Files)
- Click "Add Node" and search for Google Drive.
- Select "Google Drive Trigger" and add it to the workflow.
- Authenticate with your Google Account.
- Select the folder to monitor.
- Set the trigger to activate whenever a new file is added.
- Click "Execute Node" to test.
- Click "Save".
Step 2: IF Node (Check if File is a PDF)
- Click "Add Node" and search for IF.
- Add a condition to check if the file extension is .pdf
- If true → Send the file to the next step.
- If false → Stop the workflow.
- Click "Execute Node" to test.
- Click "Save".
Step 3: HTTP Request Node (Convert PDF to HTML)
- Click "Add Node" and search for HTTP Request.
- Set the Method to POST.
- Enter the PDF.co API endpoint for PDF to HTML conversion.
- In the Headers, add API key which we have get from pdf.co
- Send the binary PDF data as the request body.
- Click "Execute Node" to test.
- Click "Save".
Step 4: Function Node (Convert Response to Binary)
- Click "Add Node" and search for Function.
- Write a JavaScript function to transform the API response into a binary file.
- Click "Execute Node" to test.
- Click "Save".
Step 5: Google Drive Node (Save Converted HTML File)
- Click "Add Node" and search for Google Drive.
- Select "Upload File" as the action.
- Authenticate with your Google Account.
- Set the destination folder for storing the HTML file.
- Map the binary data from the Function Node.
- Click "Execute Node" to test.
- Click "Save".
Step 6: Connect & Test the Workflow
- Link the nodes in this order (Google Drive Trigger → IF Node → HTTP Request → Function Node → Google Drive Upload)
- Run the workflow manually.
- Upload a test PDF to Google Drive.
- Check Google Drive for the converted HTML file.
Who’s behind this?
WeblineIndia’s AI development team.
We've delivered 3500+ software projects across 25+ countries since 1999. From no-code automations to complex AI systems — our AI team builds tools that drive results.
Looking to hire AI developers? Start with us.
Share Template
More Building Blocks workflow templates
Creating an API endpoint
Task:
Create a simple API endpoint using the Webhook and Respond to Webhook nodes
Why:
You can prototype or replace a backend process with a single workflow
Main use cases:
Replace backend logic with a workflow
Jonathan
Very quick quickstart
Want to learn the basics of n8n? Our comprehensive quick quickstart tutorial is here to guide you through the basics of n8n, step by step.
Designed with beginners in mind, this tutorial provides a hands-on approach to learning n8n's basic functionalities.
Deborah
+10
Building Your First WhatsApp Chatbot
This n8n template builds a simple WhatsApp chabot acting as a Sales Agent. The Agent is backed by a product catalog vector store to better answer user's questions.
This template is intended to help introduce n8n users interested in building with WhatsApp.
How it works
This template is in 2 parts: creating the product catalog vector store and building the WhatsApp AI chatbot.
A product brochure is imported via HTTP request node and its text contents extracted.
The text contents are then uploaded to the in-memory vector store to build a knowledgebase for the chatbot.
A WhatsApp trigger is used to capture messages from customers where non-text messages are filtered out.
The customer's message is sent to the AI Agent which queries the product catalogue using the vector store tool.
The Agent's response is sent back to the user via the WhatsApp node.
How to use
Once you've setup and configured your WhatsApp account and credentials
First, populate the vector store by clicking the "Test Workflow" button.
Next, activate the workflow to enable the WhatsApp chatbot.
Message your designated WhatsApp number and you should receive a message from the AI sales agent.
Tweak datasource and behaviour as required.
Requirements
WhatsApp Business Account
OpenAI for LLM
Customising this workflow
Upgrade the vector store to Qdrant for persistance and production use-cases.
Handle different WhatsApp message types for a more rich and engaging experience for customers.
Jimleuk
Pulling data from services that n8n doesn’t have a pre-built integration for
You still can use the app in a workflow even if we don’t have a node for that or the existing operation for that. With the HTTP Request node, it is possible to call any API point and use the incoming data in your workflow
Main use cases:
Connect with apps and services that n8n doesn’t have integration with
Web scraping
How it works
This workflow can be divided into three branches, each serving a distinct purpose:
1.Splitting into Items (HTTP Request - Get Mock Albums):
The workflow initiates with a manual trigger (On clicking 'execute').
It performs an HTTP request to retrieve mock albums data from "https://jsonplaceholder.typicode.com/albums."
The obtained data is split into items using the Item Lists node, facilitating easier management.
2.Data Scraping (HTTP Request - Get Wikipedia Page and HTML Extract):
Another branch of the workflow involves fetching a random Wikipedia page using an HTTP request to "https://en.wikipedia.org/wiki/Special:Random."
The HTML Extract node extracts the article title from the fetched Wikipedia page.
3.Handling Pagination (The final branch deals with handling pagination for a GitHub API request):
It sends an HTTP request to "https://api.github.com/users/that-one-tom/starred," with parameters like the page number and items per page dynamically set by the Set node.
The workflow uses conditions (If - Are we finished?) to check if there are more pages to retrieve and increments the page number accordingly (Set - Increment Page).
This process repeats until all pages are fetched, allowing for comprehensive data retrieval.
Jonathan
Joining different datasets
Task:
Merge two datasets into one based on matching rules
Why:
A powerful capability of n8n is to easily branch out the workflow in order to process different datasets. Even more powerful is the ability to join them back together with SQL-like joining logic.
Main use cases:
Appending data sets
Keep only new items
Keep only existing items
Jonathan
+11
Back Up Your n8n Workflows To Github
This workflow will backup your workflows to Github. It uses the public api to export all of the workflow data using the n8n node.
It then loops over the data checks in Github to see if a file exists that uses the workflow name. Once checked it will then update the file on Github if it exists, Create a new file if it doesn't exist and if it's the same it will ignore the file.
Config Options
repo_owner - Github owner
repo_name - Github repository name
repo_path - Path within the Github repository
>This workflow has been updated to use the n8n node and the code node so requires at least version 0.198.0 of n8n
Jonathan
