Automation library · Money admin

Generate custom branded PDF invoices

Started by another system calling it, and works across Email. 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 1Logic 3Service 8

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

  1. 1Listen for New QuickBooks InvoiceWebhookStarts it
  2. 2Get Invoice Data from QuickBooksQuickbooksService
  3. 3Fetch Company Logo ImageHttp RequestService
  4. 4Fetch Company Signature ImageHttp RequestService
  5. 5Combine Invoice, Logo & SignatureMergeLogic
  6. 6Convert Logo to Base64Extract From FileService
  7. 7Convert Signature to Base64Extract From FileService
  8. 8Prepare All Data for TemplateCodeLogic
  9. 9Build HTML Invoice from DataHtmlLogic
  10. 10Convert HTML to Binary FileConvert To FileService
  11. 11Generate PDF via GotenbergHttp RequestService
  12. 12Email PDF Invoice to CustomerEmail SendService

How it's built

Starts on
Another system calling it
Steps
12
Size
Medium: a working afternoon
Connects to
Email
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Email 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.