Automation library · Research and reporting

Turn form submissions into branded PDF reports with PDFMint

Started by someone submitting a form. It calls services over plain HTTP rather than through connectors. 11 steps, 3 branches: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
3Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Logic 6Service 4

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

  1. 1Collect the reportForm triggerStarts it
  2. 2Set report brandingSetLogic
  3. 3Check the submission is completeIfLogic
  4. 4Check remaining quotaPdf MintService
  5. 5Explain what went wrongSetLogic
  6. 6Is there quota left?IfLogic
  7. 7Show the errorFormService
  8. 8Build the Markdown reportCodeLogic
  9. 9Render Markdown to PDFPdf MintService
  10. 10Did the render succeed?IfLogic
  11. 11Hand back the PDFFormService

How it's built

Starts on
Someone submitting a form
Steps
11, with 3 branches
Size
Medium: a working afternoon
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on someone submitting a form.

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. 11 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 11 steps before you point it at anything that matters.