Automated Expedia Travel Receipt Exports
Every Monday, WebRun signs into Expedia, finds trips that finished in the past week, opens each itinerary for the receipt total, confirmation number and travel dates, files one expense ready row per booking in Airtable, and posts the batch summary to a Notion page finance can work from.
How do I collect travel receipts for expenses without searching my email?
WebRun gets travel receipts to finance every Monday. It finds Expedia trips that finished in the past week, reads each itinerary for the total charged, confirmation number and dates, files one expense ready row per booking in Airtable, and posts the batch summary in Notion.
- Expense claims take minutes instead of an email trawl
- Every booking carries its confirmation number and amount
- Unclear receipts are flagged instead of quietly missed
Built for office managers · frequent business travellers · finance teams · small agencies
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.expedia.com/user/loginin a real browser with your saved login - no setup, no API keys. -
1
Expedia - pull receipts from finished trips
expedia.com
WebRun opens Expedia to pull receipts from finished trips. - Sign into Expedia and open your trips list
- Find trips whose travel dates finished in the past week
- Open each itinerary and read the total charged, the confirmation number and the dates
- Separate flights, hotels and cars so each line can be coded properly
- Skip trips already exported on a previous run
Done when Every finished trip has its bookings captured with amounts and confirmation numbers.
-
2
Airtable - file one row per booking
airtable.com
WebRun opens Airtable to file one row per booking. - Open the expenses base in Airtable
- Create one row per booking with the traveller, dates, amount, currency and confirmation number
- Set the booking type so flights, hotels and cars are coded separately
- Flag rows where the receipt total could not be read so a person checks the itinerary
- Mark each row unsubmitted. WebRun never files an expense claim
Done when Every booking from the week is a row ready to be claimed.
-
3
Notion - log the batch for finance
notion.so
WebRun opens Notion to log the batch for finance. - Open the finance handover page in Notion
- Post this week's batch: number of trips, number of bookings and the total value
- List any booking flagged for a missing or unclear amount
- Leave the batch for finance to review. Nothing is submitted to an expense system
Done when Finance has this week's receipt batch summarised in Notion.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it submit expense claims?
No. WebRun files the rows and marks them unsubmitted. Filing the claim in your expense system is a human step, so nothing is claimed or approved without a person doing it.
Can it book, change or cancel a trip?
No. It reads finished itineraries only. WebRun never books travel, changes a reservation, cancels anything, or touches a stored payment method on the account.
What if a receipt total is unclear?
The row is still created and flagged, and the booking is listed in the Notion batch summary so a person opens that one itinerary instead of checking them all.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.