Automation library · Content

Upload documents with Postgres

Started by someone submitting a form, and works across Postgres. 12 steps, 3 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 2Logic 8Service 2

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

  1. 1Document Upload FormForm triggerStarts it
  2. 2Webhook UploadWebhookStarts it
  3. 3Workflow ConfigurationSetLogic
  4. 4Check File SizeIfLogic
  5. 5Check MIME TypeIfLogic
  6. 6Return Validation ErrorSetLogic
  7. 7Generate Document MetadataCodeLogic
  8. 8Check for DuplicatePostgresService
  9. 9Is Duplicate?IfLogic
  10. 10Return Duplicate ResponseSetLogic
  11. 11Insert Document RecordPostgresService
  12. 12Return Success ResponseSetLogic

How it's built

Starts on
Someone submitting a form
Steps
12, with 3 branches
Size
Medium: a working afternoon
Connects to
Postgres
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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