Every stag do has the same problem, and it is not the one you think. It is not the money or the dates. It is that a group chat will never agree on a destination before the cheap flights have gone, and the person organising it ends up refreshing Ryanair every other evening.
I was that person. So I built a bot instead.
The actual problem
Living in Devon, the useful airports are Exeter, Newquay and Bristol. Between them the destinations are limited and they change: routes come and go by season, new ones get announced, and each new season’s schedule goes on sale at a moment you only find out about if you happen to be looking. The cheapest seats are there at the start, before everyone else notices.
What I wanted was simple: tell me when a new destination appears from any of those three airports, and tell me when a new schedule is released, so the group chat could be handed a shortlist while the prices were still silly.
What it does
It is an n8n workflow that watches two kinds of source.
Ryanair itself, for the routes it currently flies from Exeter, Newquay and Bristol, and for new schedules going on sale.
The airports’ own websites, because an airport often announces a new route before the airline has put it on sale. Watching both means hearing about a route at the announcement, not at the booking page.
Every route the bot knows about is a row in a Notion database. Each run compares what the sources say now against that list, and anything new goes two places: into Notion, so it counts as known next time, and out to Telegram as a message.
That is the same pattern as the template scanner: a source that changes, a record of what has been seen, a diff between them, and a notification to the place you actually look. Once you have built one of these, the second is mostly a matter of pointing it at something else.
Why schedules matter more than routes
A new destination is exciting. A new schedule going on sale is what actually moves the price. The day a season opens, the fares are at their lowest and nobody has booked yet. A week later the group chat is still arguing and the cheap seats have gone.
So the alerts that earn their keep are not “you can now fly somewhere new”, they are “the next batch of flights from Bristol just went on sale”. That message, arriving on the day it happens, beats every person in the chat checking the site when they remember to.
Things it deliberately does not do
It does not book anything. It is a watcher. Buying flights automatically, on a card, for a group, is the kind of automation that is fun right up until it is not. The decision stays with people. The bot just makes sure they are deciding early.
It does not try to track every fare on every route. That would be a much bigger, much heavier thing, and the question it answers is smaller than that: has something new appeared? Small questions make for reliable automations.
It is polite to the sites it reads. These are websites built for people booking holidays, not for bots. Routes do not change by the minute, so there is no reason to check by the minute. A scanner that runs quietly and infrequently is one that keeps working.
Why I am writing this on a business blog
Because it is the same automation I sell, in a party hat. Swap Ryanair for a supplier’s price list, the airports for a competitor’s website and Telegram for the ops channel in Slack, and it is a stock alert or a pricing monitor for a business. The pattern is identical; only the stakes change.
If there is something you keep checking by hand, the version of this for your business is usually a small build. Say hello. And if you are organising a stag do, I am afraid the bot is not for hire, but the group chat will not agree on a destination either way.