Automation library · Integrations

Optimise images added to a Google Drive folder

Started by an event in a connected app, and works across Google Drive. 5 steps: small enough to read in one sitting and change without fear.

Small

5 stepsSmall: readable in one sitting
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Service 4

The steps in the order they run, from what starts it.

  1. 1Check GDrive for new imagesGoogle Drive triggerStarts it
  2. 2Download imageGoogle DriveService
  3. 3Optimise - Send image to TinyPNGHttp RequestService
  4. 4Get optimised image from tinyPNGHttp RequestService
  5. 5Google DriveGoogle DriveService

How it's built

Starts on
An event in a connected app
Steps
5
Size
Small: readable in one sitting
Connects to
Google Drive
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Drive account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Not long. At 5 steps it can be read in one sitting and changed without fear.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 5 steps before you point it at anything that matters.