src ▸ task opened 0

Automate Google Flights

Turn the repetitive Google Flights work you do by hand (search a route and dates, read fares) into a workflow Writ runs for you, on your own account, on a schedule or on demand.

Automate Google Flights See how it works
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Google Flights workflow
  1. 1
    search a route and dates
  2. 2
    read fares
  3. 3
    compare options
  4. 4
    export results

✓ Recorded once, then run for you

gap ▸ done by hand 01
01
why

Stop doing Google Flights by hand

The Google Flights tasks you repeat (search a route and dates, read fares, compare options) are exactly the kind of work a computer should do. But Google Flights has no general public API, and the flow runs behind a login and dynamic pages. Google Flights has no public API; fares are rendered in the browser as the search completes.

Writ closes that gap. Record the Google Flights task once (or describe it to an AI session) and Writ runs it for you in a real browser, on your own account. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

ops ▸ actions mapped 02
02
automate

Google Flights tasks Writ can run for you

Each of these is a real Google Flights action, captured into a workflow and run on your own account.

{ }search a route and dates
{ }read fares
{ }compare options
{ }export results

Workflows extract structured fields such as flight fare, airline, stops, duration along the way: typed data you can route anywhere.

build ▸ three routes 03
03
build

Three ways to build your Google Flights automation

Pick whichever fits the task. All three produce the same workflow Writ can run for you.

✦Record itDo the Google Flights task once in a real browser (search a route and dates, then read fares) and the recorder captures every step into a reusable workflow.
✦Describe it to AITell an AI session your goal on Google Flights in plain language; it drives the live page and builds the workflow for you, no recording needed.
✦Discover itLet API discovery watch Google Flights's own network calls as you browse, then turn the underlying requests into a fast, headless workflow.

Built on the same engine as the recorder and workflows, with 30+ step types.

auth ▸ logged-in web 04
04
the hard web

Login, 2FA, and dynamic pages on Google Flights

The reason Google Flights is tedious to automate is the same reason most tools can't. Writ handles it.

Google Flights results are public; Writ renders them in real Chromium to capture fares and price-trend hints that populate dynamically.

PersonasTOTP & mailbox OTP AI navigationReal Chromium rendering
when ▸ it runs 05
05
when it runs

Run the Google Flights automation on your terms

On a schedule, on demand, or the instant something changes. You choose the trigger.

✦On a scheduleRun the Google Flights task every hour, every morning, or any cadence. No one has to remember to do it.
✦On demandTrigger a single run from the dashboard, a webhook, your code, or an AI agent, whenever you need it.
✦On a changeWatch Google Flights for fare drop or price-trend change and fire the automation the instant it happens.
  1. 1
    Build the Google Flights workflow once

    Record the task, describe it to AI, or discover it from the network. Writ captures each step, including login and 2FA, into a workflow you can edit.

  2. 2
    Run it on your terms

    Run it on demand, on a schedule, or fire it from a Monitor when Google Flights changes. It runs on your own Google Flights account, in a real browser.

  3. 3
    Call it from anything

    The same workflow is a REST endpoint at /v1/google-flights/run and an MCP tool, so your code, a no-code tool, or an AI agent can trigger the Google Flights automation too.

watch ▸ changes tracked 06
06
watch

Trigger the Google Flights automation on a change

Monitor Google Flights for fare drop, price-trend change, new lower option and run your workflow the moment it happens.

Monitors check as fast as every 10s (10s on Enterprise). A detected change becomes a trigger that runs your Google Flights automation in seconds. Monitor Google Flights ▸

venue ▸ local or cloud 07
07
run it

Free on your own machine, or on cloud

Local / BYO agent

No compute charge. The agent runs on your hardware, so it can reach Google Flights even from an intranet or VPN-only network, and your AI keys never leave your machine.

Writ cloud

Metered by running time at $0.12 per browser-hour, drawn from your plan’s included usage. No infrastructure to manage.

call ▸ endpoint too 08
08
callable

The same Google Flights automation is an API and an MCP tool

Automating Google Flights for yourself and calling it from software are the same workflow. Once you have it, publish it as a REST endpoint at/v1/google-flights/run and a matching MCP tool, so your code or an AI agent can trigger the Google Flights task too.

Google Flights API Google Flights MCP tools
also ▸ same workflow 09
09
other ways

Other ways to work with Google Flights

Google Flights APICall Google Flights as a REST endpoint from your own software.Website to API Google Flights MCP toolsExpose Google Flights as MCP tools your agent can call.For AI agents Monitor Google FlightsWatch Google Flights and act the instant it changes.Change detection Track Google Flights pricesWatch Google Flights prices and act on a drop.Price WorkflowsHow recorded workflows run, with login, 2FA, and 30+ step types.Product
faq ▸ questions answered 10
10
faq

Automating Google Flights: questions

How do I automate Google Flights?
Record the Google Flights task once in the recorder (search a route and dates, read fares, compare options) or describe your goal to an AI session. Writ turns it into a workflow it can run for you on a schedule or on demand, on your own Google Flights account. It usually takes minutes, not a backend project.
Is it allowed to automate Google Flights this way?
Collect Google Flights data you have the right to access and respect Google's Terms of Service and rate limits. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Does Google Flights automation work behind login and 2FA?
Google Flights results are public; Writ renders them in real Chromium to capture fares and price-trend hints that populate dynamically. Writ handles TOTP and mailbox-OTP two-factor through Personas, so the automation runs inside your own authenticated Google Flights session.
Can I run the Google Flights automation without writing code?
Yes. Recording and AI sessions need no code at all. If you do want to trigger it from software, the same workflow is a REST endpoint and an MCP tool, but that is optional.
Where does it run, and what does it cost?
Run it on your own machine with a local or BYO agent for no compute charge, useful when Google Flights is only reachable from your network or VPN. Or run it on metered cloud at $0.12 per browser-hour, drawn from your plan’s included usage. Start free.
rec ▸ ready ●

Automate Google Flights in minutes

Record it once, then let Writ run it for you: on a schedule, on demand, or on a change. Get started free.

Get started