Automation library · Documents and files

Translate PDF documents from Google Drive folder with DeepL

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

Medium

12 stepsMedium: a working afternoon
1Branch: places the flow splits
2Loops or waits
1Service it connects to

The flow

Starts it 1Logic 5Service 6

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

  1. 1Run manuallyManual triggerStarts it
  2. 2⚙️ configSetLogic
  3. 3Get files from specified folderGoogle DriveService
  4. 4Use only PDF documentsFilterLogic
  5. 5Download filesGoogle DriveService
  6. 6Send translate requestHttp RequestService
  7. 7Check translation statusHttp RequestService
  8. 8Wait a bitWaitLogic
  9. 9file translated?IfLogic
  10. 10Wait between documentsWaitLogic
  11. 11Get translated document from deepLHttp RequestService
  12. 12Uplad to original folderGoogle DriveService

How it's built

Starts on
An event in a connected app
Steps
12, with 1 branch, 2 loops 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. 12 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 12 steps before you point it at anything that matters.