Automation library · Data collection

Track recurring job pain points with SerpAPI and Gemini

Started by a clock, and works across Google Sheets. It hands the judgement calls to Gemini. 11 steps: a working afternoon to understand properly.

MediumCalls a model: Gemini

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

The flow

Starts it 1Model 1Logic 5Service 4

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

  1. 1Weekly TriggerSchedule triggerStarts it
  2. 2Set Search ConfigSetLogic
  3. 3Fetch Job Postings (SerpApi)Http RequestService
  4. 4Split Out JobsSplit OutLogic
  5. 5AI ModelGoogle GeminiModel
  6. 6Parse AI OutputCodeLogic
  7. 7Append to Google SheetGoogle SheetsService
  8. 8Read All Sheet RowsGoogle SheetsService
  9. 9Aggregate Sheet RowsAggregateLogic
  10. 10Rank Pain Points by FrequencyCodeLogic
  11. 11Write Summary SheetGoogle SheetsService

How it's built

Starts on
A clock
Steps
11
Size
Medium: a working afternoon
Connects to
Google Sheets
Model
Gemini

Questions

What does it need to run?

An n8n account, plus your own Google Sheets account, 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. 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.