Automation library · Content

Sync PostgreSQL data to a Pinecone vector knowledge base

Started by a clock, and works across Postgres. 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 2Logic 6Service 4

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

  1. 1Manual TriggerManual triggerStarts it
  2. 2Cron Trigger (Optional)Schedule triggerStarts it
  3. 3Workflow ConfigurationSetLogic
  4. 4Discover PostgreSQL MetadataPostgresService
  5. 5Filter Indexable TablesCodeLogic
  6. 6Fetch Table RowsPostgresService
  7. 7Build Embedding DocumentsCodeLogic
  8. 8Prepare Gemini Embedding BatchesCodeLogic
  9. 9Generate Gemini EmbeddingsHttp RequestService
  10. 10Prepare Pinecone Upsert BatchesCodeLogic
  11. 11Upsert Vectors to PineconeHttp RequestService
  12. 12Return Sync SummaryCodeLogic

How it's built

Starts on
A clock
Steps
12
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 a clock.

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.