Automation library · Content

Detect semantic duplicate website pages with Google Drive

Started by an event in a connected app, and works across Google Drive and Postgres. 29 steps, 2 loops or waits: large, and worth reading before you trust it with anything live.

LargeRetrieval

Download free
29 stepsLarge: read it before trusting it with anything live
0Branches: places the flow splits
2Loops or waits
2Services it connects to

The flow

Starts it 1Model 4Logic 7Service 17

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

  1. 1Generate Local EmbeddingsEmbeddings OllamaModel
  2. 2Chunk Text RecursivelyText Splitter Recursive Character Text SplitterModel
  3. 3Start Duplicate CheckManual triggerStarts it
  4. 4Save Document EmbeddingsVector Store PGVectorModel
  5. 5Context InjectorDocument Default Data LoaderModel
  6. 6Clear Vector TablePostgresService
  7. 7Dedup Processed ItemsRemove DuplicatesLogic
  8. 8Clear Scraped Pages TablePostgresService
  9. 9Batches for EmbeddingSplit In BatchesLogic
  10. 10Scan Source DirectoryGoogle DriveService
  11. 11Create HNSW IndexPostgresService
  12. 12Get Unprocessed Scraped TextPostgresService
  13. 13Isolate Target DocumentsFilterLogic
  14. 14Compute Chunk SimilaritiesPostgresService
  15. 15Loop Source FileSplit In BatchesLogic
  16. 16Generate Pairwise ReportPostgresService
  17. 17GDrive Download DocumentGoogle DriveService
  18. 18Fetch Chunk Similarity DataPostgresService
  19. 19Extract Raw Text ContentHtmlLogic
  20. 20Export Chunk Similarity ReportConvert To FileService
  21. 21Format Database PayloadSetLogic
  22. 22Calculate Page CentroidsPostgresService
  23. 23Save Scraped Page TextPostgresService
  24. 24Compute Centroid DistancesPostgresService
  25. 25Code in JavaScriptCodeLogic
  26. 26Aggregate Page-Level MetricsPostgresService
  27. 27Finalize Duplicate FlagsPostgresService
  28. 28Fetch Page-Level Report DataPostgresService
  29. 29Export Page-Level ReportConvert To FileService

How it's built

Starts on
An event in a connected app
Steps
29, 2 loops or waits
Size
Large: read it before trusting it with anything live
Connects to
Google Drive, Postgres
Model
None. This is plumbing, not judgement
Retrieval
Answers are drawn from documents you supply, not from the model alone

Questions

What does it need to run?

An n8n account, plus your own Google Drive and Postgres accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

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?

Take your time. At 29 steps it is large: read it before trusting it with anything live.

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