apify-google-flights-trackinglisted

# Google Flights Tracking: Your Own Fare History, With a Baseline in Every Row Schedule the deals feed, store the rows, and you own a fare record where every observation already knows what that route normally costs. ## When to use this skill - The user wants "flight price tracking" or airfare monitoring from their own data. - They are building a price-alert product and need a source feed to sit under it. - They want fare data where each row carries a reference price, not just a number. - They want to watch several home airports on one schedule. Not for: a one-shot look at today's bargains (use the companion apify-google-flights-deals skill) or pricing a specific route you have already picked (`johnvc/Google-Flights-Data-Scraper-Flight-and-Price-Search`). See `references/actor-index.md`. ## What this does and does not do An alert is two pieces: a repeated observation, and a rule about when to notify. This Actor is the observation half. It returns a snapshot each run, keeps no history, and sends nothing. You schedule it, you store the rows, and you write the rule. Any copy or agent response that implies this Actor notifies the user is wrong. The payoff for doing it this way is `average_price`. Because every observation arrives with what that route typically costs, your notify rule can be "below typical" rather than a fixed threshold you guessed at. ## What you get One dataset row per destination, per run. `result_type` separates `deal` rows from `error` rows: - `price