Automation library · Data collection

Log weekly Google Flights fare snapshots to Google Sheets

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

Medium

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

The flow

Starts it 1Logic 8Service 3

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

  1. 1Every Monday morningSchedule triggerStarts it
  2. 2Optional: keep only the cheapest per routeFilterLogic
  3. 3Optional: nonstop onlyFilterLogic
  4. 4Optional: post the cheapest to SlackSlackService
  5. 5Set the routes to watchSetLogic
  6. 6One search per routeSplit OutLogic
  7. 7Search the faresApifyService
  8. 8One item per fareSplit OutLogic
  9. 9Shape each fareCodeLogic
  10. 10Cheapest first, per routeSortLogic
  11. 11Mark the cheapest on each routeCodeLogic
  12. 12Append the faresGoogle SheetsService

How it's built

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

Questions

What does it need to run?

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