Automation library · Documents and files

Generate merged onboarding PDF packets with PDFops

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

Medium

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

The flow

Starts it 3Logic 3Service 6

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

  1. 1New Record SubmittedWebhookStarts it
  2. 2Payload Valid?IfLogic
  3. 3Fetch Blank Form AHttp RequestService
  4. 4Fetch Blank Form BHttp RequestService
  5. 5Respond With ErrorRespond To WebhookStarts it
  6. 6PDFops Fill Form APdfopsService
  7. 7PDFops Fill Form BPdfopsService
  8. 8Combine Filled FormsMergeLogic
  9. 9Both Forms Filled?IfLogic
  10. 10PDFops Merge PacketPdfopsService
  11. 11Upload Packet to DriveGoogle DriveService
  12. 12Respond SuccessRespond To WebhookStarts it

How it's built

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