Automation library · Content

Track documentation changes with Firecrawl and Postgres

Started by a clock, and works across Postgres and Telegram. It hands the judgement calls to Gemini. 13 steps, 1 branch: a working afternoon to understand properly.

MediumCalls a model: Gemini

Download free
13 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Model 1Logic 7Service 4

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

  1. 1Schedule Daily 9AMSchedule triggerStarts it
  2. 2Firecrawl Map DocsFirecrawlService
  3. 3Split & Filter LinksCodeLogic
  4. 4Firecrawl Scrape PageFirecrawlService
  5. 5Hash ContentCodeLogic
  6. 6Postgres Upsert & DiffPostgresService
  7. 7Filter Changed PagesFilterLogic
  8. 8Aggregate ChangesAggregateLogic
  9. 9IF Has ChangesIfLogic
  10. 10Format Changes ListCodeLogic
  11. 11No Changes DetectedNo OpLogic
  12. 12Gemini Summarize ChangesGoogle GeminiModel
  13. 13Send Telegram AlertTelegramService

How it's built

Starts on
A clock
Steps
13, with 1 branch
Size
Medium: a working afternoon
Connects to
Postgres, Telegram
Model
Gemini

Questions

What does it need to run?

An n8n account, plus your own Postgres and Telegram accounts, and a key for Gemini. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

Yes. It calls Gemini. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 13 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 13 steps before you point it at anything that matters.