Automation library · Integrations

Split PDFs with PDF4me and Google Drive

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

Medium

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

The flow

Starts it 5Logic 3Service 4

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

  1. 1On dedicated webpage openWebhookStarts it
  2. 2On PDF file uploadedWebhookStarts it
  3. 3ConfigSetLogic
  4. 4Split PDFPdf4meService
  5. 5Serve web form for PDF uploadRespond To WebhookStarts it
  6. 6Search Google Drive for old temp filesGoogle DriveService
  7. 7Prepare Files to uploadCodeLogic
  8. 8Respond when PDF API ErrorRespond To WebhookStarts it
  9. 9Delete old temp filesGoogle DriveService
  10. 10Upload files to temp driveGoogle DriveService
  11. 11Prepare webpage with links to filesCodeLogic
  12. 12Serve webpage with links to filesRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
12
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 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. 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.