WORKFLOWS / TRAVEL AND LOGISTICS
Replan business travel after a disruption.
When a flight changes, compare realistic ways to finish the trip. AI helps work through routes, timing, and knock-on effects. You confirm availability and approve bookings before anything changes.
WHAT THIS WORKFLOW PRODUCES
A recovery plan you can act on.
Show up to three viable options, with the next action for each. Include the last verification time and anything that still needs checking. Each real option should carry the flight or service, local departure and arrival times, estimated arrival at the final destination, total estimated cost, source, and time checked. Hide options that violate a hard constraint. The rows below are comparison categories, never live flight offers.
TRIP RECOVERY · THREE WAYS TO FINISH
OPTIONS CHECKED 4:12 PM
THE OPERATING METHOD
Understand the workflow without AI.
This is the method itself, runnable with the airline app, a map, and a phone. It goes fastest when the trip details, the contacts, and the policy limits are already in one place; the third level below prepares that before the trip. AI is introduced only after the method makes sense on its own.
Confirm the disruption
Check what changed and where the traveler is right now.
YOUSet the constraints
Establish the latest useful arrival, acceptable airports, ground travel, budget, and any non-negotiables.
YOUFind viable routes
Consider the full journey, including the time needed to leave the aircraft, collect bags, change terminals, or reach another airport.
YOUVerify and choose
Confirm a bookable option, its total cost, and the effect on existing reservations.
YOUUpdate the trip
Complete approved changes and tell the people affected.
YOUScheduled arrival is not the same as being outside the airport and ready to leave. A shorter flight itinerary can produce a longer journey overall.
WHERE THE FACTS LIVE
Use the systems where the work already lives.
The tools below serve different purposes. Flight tracking shows operations; the airline or booking provider confirms a bookable offer. Connections, data coverage, and paid access vary. Named tools link to their pages in the library.
TRIP DETAILS
Airline confirmations
The organization's travel platform
Approved traveler preferences
STATUS AND DISRUPTION
The operating airline
Airport notices
FAA airport status
National Weather Service information
RECOVERY OPTIONS
Airline booking results or the travel desk
Rental-company locations
Ground-transport estimates
Google Maps
The travel policy
THREE WAYS TO RUN IT
Choose how much machine.
This is the most time-critical workflow in the library. Level 1 turns the situation into a search plan. Level 2 compares options a person has checked. Level 3 prepares a recovery kit before each trip, so that on the day the first two levels start with the facts already in hand. No level books anything, and no version replaces the airline or the travel desk. The tools named are examples. Use what your organization already runs, provided the connection is supported and approved.
LEVEL 1
Work out what to check.
Give AI the relevant itinerary and confirmed situation. It identifies possible recovery approaches and the information needed to rule them in or out. You check live options.
Use this version when a trip has just gone wrong and you need a clear way to work through alternatives.
WHAT THIS VERSION REDUCES
Missing a plausible route or forgetting a constraint while searching under pressure.
WHAT A PERSON STILL DOES
Checks current services, confirms availability, speaks to the traveler, and books.
MAIN LIMITATION
A plausible route is only a search suggestion. AI must not invent a flight, seat, fare, or open rental counter.
Build this version, step by step 5 steps, one action each. Prompts carry a Copy button.
Tell the AI what is confirmed right now.
WHAT TO GIVE IT
Where the traveler is, the flight date and number, and the latest update from the airline. Say whether the traveler can leave the aircraft or the terminal yet. If you do not know when they will be released, say that too.
Set the limits the plan has to respect.
THE LIMITS
Where they need to be and by when, which nearby airports are acceptable, how far they can travel by road, what they are allowed to spend, what they are carrying, and whether an overnight stop is acceptable. Leave passport and payment details out.
Ask for a search plan rather than an answer.
Identify up to three recovery approaches that fit these constraints. Separate confirmed facts from assumptions. Include time to leave the airport and reach the final destination. Do not invent schedules, fares, availability, or rental opening hours. List the checks needed before each approach could be booked.
Check each route with the airline or the travel desk.
THE CHECK
- The flight is operating.
- A seat can be booked.
- Any car rental or transfer is open at that hour.
Drop the routes that fail.
Choose with the traveler.
THE DECISION
Lay out the remaining options and their trade-offs in a few lines. Do not buy a second flight on the assumption that the traveler will be off the first one in time.
LEVEL 2
Compare verified recovery options.
Let AI retrieve the approved itinerary and business commitments, then compare options you or a connected service have checked. It helps identify which route gets the traveler to the right place at a useful time.
Use this version when several routes are possible and the full journey is difficult to compare quickly.
WHAT THIS VERSION REDUCES
Comparing scattered options, calculating practical arrival, and overlooking meetings or onward arrangements affected by the disruption.
WHAT A PERSON STILL DOES
Validates availability, accepts the tradeoffs, and authorizes purchases and cancellations.
MAIN LIMITATION
Flight tracking does not provide a guaranteed seat offer. Even a priced offer can change before purchase.
CONNECTION EXAMPLE
Claude's Google connections can read the itinerary email and the calendar, and a Microsoft 365 connection does the same. Neither connects to airline seat inventory. Live flight offers come from the airline or the travel desk, checked by a person and handed to the AI.
Build this version, step by step 5 steps, one action each. Prompts carry a Copy button.
Let the AI read the trip details from email and calendar.
EXAMPLE
An approved email connection finds the itinerary; a calendar connection finds the first commitment after arrival. Ask only about the dates and the trip in question. If a Level 3 trip page exists, start from it: the facts are already checked.
Give it the options a person has already checked.
WHAT EACH OPTION RECORDS
The route, the fare, the seats available when you looked, the conditions, and where the information came from, from the airline or the travel desk. An AI assistant with approved browsing can help find public information, but anything behind a login is still a manual check.
Ask it to compare the whole journey.
WHAT THE COMPARISON COVERS
Getting to the airport, security, connection time, bags, ground travel at the other end, timezones, extra costs, and any effect on the business schedule. Estimates are labeled as estimates.
Ask the one question that decides it.
Which checked option reaches the destination earliest without requiring an unconfirmed early release from the aircraft?
Keep a fallback if the preferred option becomes unavailable.
Check again right before you buy.
THE CHECK
- The provider has confirmed the offer.
- The traveler can physically reach it in time.
- You know what happens to the original reservation.
Draft the meeting and pickup changes now, but send them only once the new plan is confirmed.
CAPABILITIES CHECKED AGAINST OFFICIAL DOCUMENTATION
Claude's Google Workspace connection documents retrieval of email and calendar context; it does not connect to airline ticket inventory. Source, checked September 5, 2026.
Claude's Microsoft 365 connection documents retrieval of mail and calendar context as another route. Source, checked September 5, 2026.
LEVEL 3
Prepare the recovery kit before every trip.
A disruption is handled fastest by the person who already has the trip in one place. The evening before a flight, a scheduled run pulls the booking, the first commitment after arrival, the policy limits, and the contacts into one trip page for a two-minute review. When something changes, the airline app sends the alert it already sends, and Level 2 runs in minutes with nothing to look up.
Use this version when the executive travels often enough that assembling the same facts before every trip is a recurring job.
WHAT THIS VERSION REDUCES
The twenty minutes of gathering that happens after the alert, when it is worth the most.
WHAT A PERSON STILL DOES
Checks the kit, confirms every seat, fare, and booking with the airline when the time comes, and decides with the traveler.
MAIN LIMITATION
The kit is only as current as the booking email it was built from. A change made by phone with the airline does not reach it unless someone updates the page.
TOOL OPTIONS
This version uses n8n or Make, Gmail, Google Calendar, an approved AI model, and a Notion page or a shared document. Outlook and a SharePoint page do the same job. Paid flight-status feeds such as FlightAware AeroAPI exist, but they only repeat the alert the airline app already sends, so they are left out.
WHAT THE KIT IS NOT
It is not a booking and not a promise of seats. Every route in it is a place to look, and every fare and availability is checked with the airline or the travel desk at the moment of need, never assumed from the page.
Build this version, step by step 6 steps, one action each. Prompts carry a Copy button.
Decide what counts as a trip.
THE TRIGGER
A calendar event that carries a flight number, or a booking confirmation filed under one Gmail label. Each trip gets one page in the travel section the office already keeps.
Schedule the run for the evening before.
THE SCHEDULE
Every day at 6 PM in the account's timezone, the workflow looks for tomorrow's calendar events with a flight number and, for each one, finds the booking email under the label. If there is no flight tomorrow, nothing runs.
Let it collect the trip's own facts.
WHAT THE RUN READS
From the booking email: the flights, confirmation numbers, seats, and fare rules. From the calendar: the first commitment after landing and who is hosting it. From the travel policy: spending limits, permitted airports, and overnight rules. From the office contact list: the driver, the hotel, the travel desk, and after-hours support.
Ask the AI step for a kit rather than a plan.
From these facts only, write the recovery kit for this trip: each segment with its confirmation number; the first commitment and the latest useful arrival; the airline's rebooking channels; alternate airports within policy; the overnight allowance; who to call, in order; and what to check first if a segment slips. Do not invent flights, fares, or availability. Mark anything not in the sources as "not in the sources".
Give the kit a two-minute review.
THE CHECK
- The confirmation numbers match the booking.
- The first commitment and its host are right.
- The policy limits are current.
Pin the kit to the trip page and send the traveler the short version.
When something goes wrong, start from the kit.
ON THE DAY
The airline app is the alert. Open the kit: the limits and the contacts are already written, so go straight to Level 2. Check options with the airline or the travel desk, choose with the traveler, and update the page. After the trip, archive the page and delete any personal details you no longer need.
CAPABILITIES CHECKED AGAINST OFFICIAL DOCUMENTATION
n8n's Google Calendar node documents reading events for a date range. Source, checked September 6, 2026.
n8n's Gmail node documents reading messages by label and search. Source, checked September 6, 2026.
n8n Cloud is a paid subscription; the self-hosted community edition is free. Source, checked September 6, 2026.
WORKS EVEN BETTER WITH
Once the replacement route is chosen, check the arrangements around it and keep the contacts needed for the rest of the trip close at hand.
Reconfirm everything after a travel change → | Keep recovery contacts beside the itinerary →