Automation library · Alerts and monitoring

Triage stale property listings with Google Sheets and Gemini

Started by a clock, and works across Google Sheets and Slack. 11 steps: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 2Logic 3Service 6

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

  1. 1When Error OccursError triggerStarts it
  2. 2Every Day at 8 AMSchedule triggerStarts it
  3. 3Post Error to SlackSlackService
  4. 4Read Listings from SheetsGoogle SheetsService
  5. 5Compute Listing MetricsCodeLogic
  6. 6Update Trend Snapshot in SheetsGoogle SheetsService
  7. 7Filter Listings Needing ReviewFilterLogic
  8. 8Post to Gemini APIHttp RequestService
  9. 9Set AI Response FieldSetLogic
  10. 10Notify via SlackSlackService
  11. 11Update Listings Status in SheetsGoogle SheetsService

How it's built

Starts on
A clock
Steps
11
Size
Medium: a working afternoon
Connects to
Google Sheets, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Sheets and Slack accounts. 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. 11 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 11 steps before you point it at anything that matters.