Automated DiDi Trip Expense Export
Every Monday, WebRun signs in to your DiDi account, opens the trip history for the week just ended, captures the date, route, fare and receipt reference for each ride, adds one row per trip to your Airtable expenses base, and builds a Notion claim summary with the weekly total ready for a person to submit.
How do I turn my ride history into an expense claim?
WebRun prepares your ride expenses every Monday. It opens your DiDi trip history for the week just ended, captures the date, route, fare and receipt reference of every completed trip, logs each in Airtable, and builds a totalled claim summary in Notion for you to review and submit.
- A totalled claim is ready every Monday without opening a receipt folder
- No trip is forgotten at month end because it was logged the week it happened
- Trips missing a purpose are flagged before the claim goes to finance
Built for consultants · field sales reps · frequent travellers · small business owners
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.didiglobal.comin a real browser with your saved login - no setup, no API keys. -
1
DiDi - collect last week's trips
didiglobal.com
WebRun opens DiDi to collect last week's trips. - Sign in to your DiDi account and open trip history
- Set the window to the week just ended
- Capture the date, time, pickup, drop-off, fare and receipt reference for each completed trip
- Skip cancelled trips and anything already exported in an earlier run
Done when Every completed trip from last week is captured with its fare and receipt reference.
-
2
Airtable - log each ride and fare
airtable.com
WebRun opens Airtable to log each ride and fare. - Open your expenses base in Airtable
- Add one row per trip with date, route, fare, receipt reference and a blank purpose field
- Tag rows using your rules, for example airport trips as travel and evening trips as client visits
- Leave the purpose blank rather than guessing when no rule matches
Done when Every trip from last week has exactly one row in the Airtable base.
-
3
Notion - build the claim summary
notion.so
WebRun opens Notion to build the claim summary. - Open your expenses workspace in Notion
- Create a claim page for the week with the itemised trips and a total
- List separately any trip missing a purpose so you can fill it in before submitting
- Leave the claim unsubmitted. WebRun prepares it and a person files it
Done when A totalled claim page for the week is waiting in Notion for review.
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 the expense claim?
No. WebRun builds the itemised claim page in Notion and stops there. Filing it with finance is a person's job, so nothing is submitted or approved without you.
Can it book or cancel a ride?
No. WebRun only reads completed trip history. It never books a trip, never cancels one, never changes a payment method and never touches a fare.
What if a trip has no business purpose recorded?
It is listed separately rather than guessed. Trips that match none of your tagging rules go into a short section at the top of the claim page for you to label before submitting.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.