Automation library · Integrations

Enhance Google Drive images with Gemini

Started by an event in a connected app, and works across Google Drive. 15 steps, 1 loop or waits: a working afternoon to understand properly.

Medium

15 stepsMedium: a working afternoon
0Branches: places the flow splits
1Loop or waits
1Service it connects to

The flow

Starts it 1Logic 6Service 8

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

  1. 1initManual triggerStarts it
  2. 2promtSetLogic
  3. 3origin_folderGoogle DriveService
  4. 4destination_folderGoogle DriveService
  5. 5get filesHttp RequestService
  6. 6map tableCodeLogic
  7. 7FilterFilterLogic
  8. 8config-dataSetLogic
  9. 9Loop Over ItemsSplit In BatchesLogic
  10. 10download-fileGoogle DriveService
  11. 11to base64Extract From FileService
  12. 12banana-requestHttp RequestService
  13. 13map-banana-responseSetLogic
  14. 14to fileConvert To FileService
  15. 15upload-resultGoogle DriveService

How it's built

Starts on
An event in a connected app
Steps
15, 1 loop or waits
Size
Medium: a working afternoon
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?

Plan an afternoon. 15 steps is enough that you should read each one before running it.

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 15 steps before you point it at anything that matters.