← All N8N workflows
Media & contentGoogle DriveGoogle Drive TriggerHTTP Request

Optimise images uploaded to GDrive

Configured with Google Drive, Google Drive Trigger, HTTP Request. Review the connections and setup before adapting this template.

Workflow preview
TriggerCheck GDrive for newimagesGoogle Drive TriggerFiles / mediaDownload imageGoogle DriveWeb / APIOptimise - Send imageto TinyPNGHTTP RequestWeb / APIGet optimised imagefrom tinyPNGHTTP RequestFiles / mediaGoogle DriveGoogle Drive

Node categories in this workflow

  • Trigger
  • Files / media
  • Web / API

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Check GDrive for new imagesTriggerGoogle Drive TriggerSee node parameters
Download imageFiles / mediaGoogle Drivedownload
Optimise - Send image to TinyPNGWeb / APIHTTP RequestPOST
Get optimised image from tinyPNGWeb / APIHTTP RequestSee node parameters
Google DriveFiles / mediaGoogle DriveSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • googleDriveOAuth2Api

Workflow notes

Automatically optimise images uploaded to Google drive folder

Automatically optimise images uploaded to Google drive folder

Each time an image is added to a google drive folder, this workflow will send it to tinypng.com to optimise the size and resave it to a google drive location of your choice.

1. Pre-setup: Google Drive credentials

1. Pre-setup: Google Drive credentials

a. Firstly you'll need to setup Google Drive credentials. Best thing is to read n8n docs to to do that. b. Once you're successfully connecting to your GDrive account, set all 3 of the Drive nodes to connect using that credential.

2. Choose the Google Drive folder n8n is going to watch for new files

2. Choose the Google Drive folder n8n is going to watch for new files

a. Go to Google Drive and create the folder you want n8n to watch for new images b. Then you need to select that folder in the Google Drive trigger node

3. Create an API key for tinypng.com

3. Create an API key for tinypng.com

a. Visit tinypng.com and request an API key b. Update the "Authorisation" parameter value with your api key. It will be in the format of "Basic REPLACE_WITH_CREDENTIAL_IN_BASE_64"

4. Choose your Google Drive folder to save your upload your optimised images to

4. Choose your Google Drive folder to save your upload your optimised images to

a. Finally, create and select the folder that you want your optimised images to be saved to b. OPTIONAL: You can also change the formatting of the name that you set. By default it will use the original file name then -optimised

Optimise images uploaded to GDrive

Optimise images uploaded to GDrive

Purpose and structure

This folder contains the Optimise images uploaded to GDrive workflow. Its executable nodes use googleDrive, googleDriveTrigger, httpRequest. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Check GDrive for new images

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/1458_HTTP_Stickynote_Import_Webhook.json MIT; preserve source notices.

More in Media & content