Automation library · CRM

Generate & edit images with Google Drive

Started by another system calling it, and works across Email and Google Drive. 14 steps, 1 branch: a working afternoon to understand properly.

Medium

14 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 2Logic 5Service 7

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

  1. 1WebhookWebhookStarts it
  2. 2If Image File Was UploadedIfLogic
  3. 3Extract from FileExtract From FileService
  4. 4Nano 🍌: Prompt OnlyHttp RequestService
  5. 5CodeCodeLogic
  6. 6Edit Fields2SetLogic
  7. 7Nano 🍌Http RequestService
  8. 8Convert to FileConvert To FileService
  9. 9Edit Fields1SetLogic
  10. 10Upload fileGoogle DriveService
  11. 11Share fileGoogle DriveService
  12. 12Edit FieldsSetLogic
  13. 13Send emailEmail SendService
  14. 14Respond to WebhookRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
14, with 1 branch
Size
Medium: a working afternoon
Connects to
Email, Google Drive
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

What starts it?

It starts on another system calling it.

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