Automation library · Documents and files

Generate PDF documents from HTML with PDF Generator API

Started by another system calling it, and works across Gmail and Postgres. 10 steps, 1 branch: a working afternoon to understand properly.

Medium

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

The flow

Starts it 2Logic 2Service 6

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

  1. 1Receive Document Request (Webhook)WebhookStarts it
  2. 2Verify Client EmailHunterService
  3. 3Email Is Valid?IfLogic
  4. 4Load HTML TemplatePostgresService
  5. 5Respond – Invalid EmailRespond To WebhookStarts it
  6. 6Populate HTML TemplateCodeLogic
  7. 7Convert HTML to PDFPdf Generator ApiService
  8. 8Upload PDF to Supabase StorageHttp RequestService
  9. 9Send PDF to Client EmailGmailService
  10. 10Record Document TransactionPostgresService

How it's built

Starts on
Another system calling it
Steps
10, with 1 branch
Size
Medium: a working afternoon
Connects to
Gmail, Postgres
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail and Postgres 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. 10 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 10 steps before you point it at anything that matters.