Google Sheets node
HTTP Request node
Google Drive node
+4

Automated Image Optimizer: convert JPG/PNG to WebP with APYHub and Google Drive

Published 2 days ago

Created by

n3witalia
Davide

Template description

This workflow automates the process of converting images from JPG/PNG format to WEBP using the APYHub API. It retrieves image URLs from a Google Sheet, converts the images, and uploads the converted files to Google Drive.

This workflow is a powerful tool for automating image conversion tasks, saving time and ensuring that images are efficiently converted and stored in the desired format.

Using WebP images on a website provides several SEO benefits:

  1. Faster Loading Speed – WebP files are smaller than JPG and PNG, reducing page load times and improving user experience.
  2. Better Core Web Vitals – Google prioritizes websites with good performance metrics like LCP (Largest Contentful Paint).
  3. Improved Mobile Performance – Smaller images consume less bandwidth, enhancing mobile usability.
  4. Higher Search Rankings – Faster sites tend to rank better on Google due to improved user experience.
  5. Reduced Server Load – Lighter images lower hosting and CDN costs while improving site efficiency.

Below is a breakdown of the workflow:


1. How It Works

The workflow is designed to convert images from JPG/PNG to WEBP format and manage the converted files. Here's how it works:

  1. Manual Trigger:

    • The workflow starts with a Manual Trigger node, which initiates the process when the user clicks "Test workflow."
  2. Set API Key:

    • The Set API KEY node defines the API key required to access the APYHub API.
  3. Get Images:

    • The Get Images node retrieves a list of image URLs from a Google Sheet. The sheet contains columns for the original image URL (FROM), the converted image URL (TO), and a status flag (DONE).
  4. Get Extension:

    • The Get Extension node extracts the file extension (JPG, JPEG, or PNG) from the image URL and adds it to the JSON data.
  5. Determine Image Type:

    • The JPG or PNG? node checks the file extension and routes the workflow to the appropriate conversion node:
      • JPG/JPEG: Routes to the From JPG to WEBP node.
      • PNG: Routes to the PNG to WEBP node.
  6. Convert Image:

    • The From JPG to WEBP and PNG to WEBP nodes send POST requests to the APYHub API to convert the images to WEBP format.
    • The API returns the URL of the converted image.
  7. Update Google Sheet:

    • The Update Sheet node updates the Google Sheet with the URL of the converted image and marks the row as done (DONE).
  8. Get Converted Image:

    • The Get File Image node downloads the converted WEBP image from the URL provided by the APYHub API.
  9. Upload to Google Drive:

    • The Upload Image node uploads the converted WEBP image to a specified folder in Google Drive.

2. Set Up Steps

To set up and use this workflow in n8n, follow these steps:

  1. APYHub API Key:

    • Obtain an API Key from APYHub.
    • In the Set API KEY node, define the API key.
  2. Google Sheets Integration:

    • Set up Google Sheets credentials in n8n for the Get Images and Update Sheet nodes.
    • Create a Google Sheet with columns for FROM (original image URL), TO (converted image URL), and DONE (status flag).
    • Provide the Document ID and Sheet Name in the Get Images node.
  3. Google Drive Integration:

    • Set up Google Drive credentials in n8n for the Upload Image node.
    • Specify the folder ID in Google Drive where the converted images will be uploaded.
  4. Test the Workflow:

    • Click the "Test workflow" button in n8n to trigger the workflow.
    • The workflow will:
      • Retrieve image URLs from the Google Sheet.
      • Convert the images to WEBP format using the APYHub API.
      • Update the Google Sheet with the converted image URLs.
      • Upload the converted images to Google Drive.
  5. Optional Customization:

    • Modify the workflow to include additional features, such as:
      • Adding more image formats for conversion.
      • Sending notifications when the conversion is complete.
      • Integrating with other storage services (e.g., Dropbox, AWS S3).

Share Template

More Building Blocks workflow templates

Webhook node
Respond to Webhook node

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
jon-n8n
Jonathan
Customer Datastore (n8n training) node

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
Deborah
HTTP Request node
WhatsApp Business Cloud node
+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
Jimleuk
HTTP Request node
Item Lists node

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.
jon-n8n
Jonathan
Merge node

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
jon-n8n
Jonathan
GitHub node
HTTP Request node
Merge node
+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
jon-n8n
Jonathan

Implement complex processes faster with n8n

red icon yellow icon red icon yellow icon