tripit-export
Export TripIt travel data (trips, flights, hotels) to JSON using browser automation. Use when the user asks to export, download, or backup their TripIt data.
What this skill does
# TripIt Export
Export all TripIt travel data (trips, flights, lodging, activities) to JSON format using TripIt's undocumented API v2.
## Trigger Phrases
- "export tripit data"
- "export my trips from tripit"
- "download tripit trips"
- `/tripit-export`
## Prerequisites
- **dev-browser plugin**: Browser automation with persistent state
- **TripIt account**: User must be able to log in to tripit.com
## API Reference
### Discovered Endpoints
```
# List upcoming trips (paginated)
GET /api/v2/list/trip?exclude_types=weather&page_size=50&past=false&traveler=true&page_num=1
# List past trips (paginated)
GET /api/v2/list/trip?exclude_types=weather&page_size=50&past=true&traveler=all&page_num=1
# Get full trip details (includes flights, lodging, activities)
GET /api/v2/get/trip/uuid/{trip-uuid}/include_objects/true?exclude_types=weather
# User profile
GET /api/v2/get/profile
```
### Response Structure
**Trip List Response:**
```json
{
"timestamp": "...",
"page_num": "1",
"page_size": "50",
"max_page": "1",
"Trip": [...]
}
```
**Trip Details Response:**
```json
{
"Trip": {...},
"AirObject": [...],
"LodgingObject": [...],
"ActivityObject": [...],
"CarObject": [...],
"RestaurantObject": [...],
"NoteObject": [...],
"TransportObject": [...],
"RailObject": [...],
"CruiseObject": [...]
}
```
## Workflow
### Step 1: Launch Browser and Authenticate
Navigate to TripIt and have the user log in:
```typescript
import { connect, waitForPageLoad } from "@/client.js";
const client = await connect("http://127.0.0.1:9222");
const page = await client.page("tripit");
await page.goto("https://www.tripit.com/app/trips");
await waitForPageLoad(page);
console.log("Please log in to TripIt...");
```
**Tell user to log in manually, then confirm when done.**
### Step 2: Fetch All Trips
After authentication, fetch upcoming and past trips with pagination:
```typescript
async function fetchAllTrips(page, past: boolean): Promise<any[]> {
const allTrips: any[] = [];
let pageNum = 1;
let maxPage = 1;
do {
const params = new URLSearchParams({
exclude_types: "weather",
page_size: "50",
past: String(past),
traveler: past ? "all" : "true",
page_num: String(pageNum)
});
const response = await page.evaluate(async (url) => {
const res = await fetch(url, {
headers: { "Accept": "application/json" }
});
return res.json();
}, `/api/v2/list/trip?${params}`);
if (response.Trip) {
const trips = Array.isArray(response.Trip) ? response.Trip : [response.Trip];
allTrips.push(...trips);
}
maxPage = parseInt(response.max_page || "1");
pageNum++;
} while (pageNum <= maxPage);
return allTrips;
}
const upcomingTrips = await fetchAllTrips(page, false);
const pastTrips = await fetchAllTrips(page, true);
```
### Step 3: Fetch Full Trip Details
For each trip, fetch complete details:
```typescript
const tripDetails = {};
for (const trip of [...upcomingTrips, ...pastTrips]) {
const details = await page.evaluate(async (uuid) => {
const res = await fetch(
`/api/v2/get/trip/uuid/${uuid}/include_objects/true?exclude_types=weather`,
{ headers: { "Accept": "application/json" } }
);
return res.json();
}, trip.uuid);
tripDetails[trip.uuid] = {
trip: details.Trip,
flights: details.AirObject || [],
lodging: details.LodgingObject || [],
activities: details.ActivityObject || [],
cars: details.CarObject || [],
restaurants: details.RestaurantObject || [],
notes: details.NoteObject || [],
transport: details.TransportObject || [],
rail: details.RailObject || [],
cruise: details.CruiseObject || []
};
// Rate limiting
await page.waitForTimeout(500);
}
```
### Step 4: Generate Final Export
```typescript
const exportData = {
exportDate: new Date().toISOString(),
summary: {
upcomingTrips: upcomingTrips.length,
pastTrips: pastTrips.length,
totalTrips: upcomingTrips.length + pastTrips.length
},
trips: Object.entries(tripDetails).map(([uuid, details]) => ({
uuid,
name: details.trip?.display_name,
startDate: details.trip?.start_date,
endDate: details.trip?.end_date,
primaryLocation: details.trip?.primary_location,
...details
}))
};
const outputPath = `tripit-export-${new Date().toISOString().split("T")[0]}.json`;
writeFileSync(outputPath, JSON.stringify(exportData, null, 2));
```
## Output Format
```json
{
"exportDate": "2026-01-13T...",
"summary": {
"upcomingTrips": 2,
"pastTrips": 45,
"totalTrips": 47
},
"trips": [
{
"uuid": "...",
"name": "Trip Name",
"startDate": "2026-01-15",
"endDate": "2026-01-20",
"primaryLocation": "Tokyo, Japan",
"trip": { /* full trip metadata */ },
"flights": [ /* AirObject array */ ],
"lodging": [ /* LodgingObject array */ ],
"activities": [ /* ActivityObject array */ ],
"cars": [],
"restaurants": [],
"notes": [],
"transport": [],
"rail": [],
"cruise": []
}
]
}
```
## Error Handling
- **401 Unauthorized**: Session expired. Re-authenticate by navigating to TripIt login.
- **Rate limiting**: Add delays between API calls if receiving 429 errors.
- **Empty responses**: Some trips may have no flights/lodging - this is normal.
## Notes
- TripIt API v2 is undocumented and may change without notice
- Authentication is session-based (cookies) - no API key required
- Large trip histories may take several minutes to export
- The `exclude_types=weather` param reduces response size
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.