Automation library · Content

Manage job records with PostgreSQL

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

Medium

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

The flow

Starts it 7Logic 1Service 4

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

  1. 1WebhookWebhookStarts it
  2. 2SwitchSwitchLogic
  3. 3Get All JobsPostgresService
  4. 4Create JobPostgresService
  5. 5Update JobPostgresService
  6. 6Delete JobPostgresService
  7. 7Return Job ListRespond To WebhookStarts it
  8. 8Error During Fetching JobsRespond To WebhookStarts it
  9. 9Return Success ResponseRespond To WebhookStarts it
  10. 10Error during job creationRespond To WebhookStarts it
  11. 11Error during job details updateRespond To WebhookStarts it
  12. 12Error during job deletionRespond To WebhookStarts it

How it's built

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