TripIt Skill

Add travel plans to TripIt by sending structured confirmation emails to plans@tripit.com. No API keys required — just email sending capability.

How It Works

TripIt parses specially formatted emails ("TripIt Approved" format) into travel objects. This skill generates those emails; you send them with whatever email tool you have (MS Graph, Himalaya, gog, etc.).

Flow:

1. 1. User says "add my flight to TripIt"
2. You construct JSON from their details
3. INLINECODE1 generates the formatted email body
4. You send it to INLINECODE2
5. TripIt creates the trip object within seconds

Setup

The sender email must be associated with the user's TripIt account. Either:

• - The email is the one they signed up with, OR
• They've added it at TripIt → Settings → Connected Email Addresses

No other configuration needed.

Usage

Generate a flight confirmation

CODEBLOCK0

Generate a hotel confirmation

CODEBLOCK1

Generate an activity

CODEBLOCK2

Generate a multi-item email

CODEBLOCK3

Include a subject line

Add --subject to any command to get a suggested email subject:

CODEBLOCK4

Sending the Email

The script outputs the email body. You send it using whatever email tool is available.

MS Graph (Microsoft 365 users)

CODEBLOCK5

Himalaya

CODEBLOCK6

gog (Google OAuth)

CODEBLOCK7

Field Reference

See references/template-format.md for the complete field list for each object type, including required vs optional fields and formatting rules.

Supported Object Types

Type	Command	Key Required Fields
Flight	INLINECODE4	airline, flightnumber, departure/arrival airport+date+time
Hotel

hotel | hotelname, checkindate, checkoutdate | | Activity | activity | activityname, startdate | | Car Rental | car | rentalcompany, pickupdate, dropoff_date | | Rail | rail | carrier, departure/arrival date+time | | Multiple | multi | Each item needs type + that type's required fields |

Verifying Items Landed

After sending an email, confirm TripIt processed it by fetching the user's iCal feed:

1. 1. The user provides their TripIt iCal URL (found at TripIt → Settings → Calendar Feed), e.g.:

https://www.tripit.com/feed/ical/private/<hash>/tripit.ics

1. 2. Fetch the feed and look for the newly added item (match on confirmation number, dates, or summary text)
2. If the item doesn't appear after ~60 seconds, check:

- Was the sender email linked to the TripIt account? - Was the email sent as plain text (not HTML)? - Were all required fields present?

CODEBLOCK8

Tip: Store the user's iCal feed URL so you can verify future sends without asking again. The URL is stable — it doesn't change unless the user regenerates it.

Gotchas

• - Date format consistency: Use one format per email (ISO 8601 recommended: 2026-03-15)
• Sender email must be linked: TripIt ignores emails from unrecognized addresses
• Plain text only: Send as plain text, not HTML
• Multi-line fields: End with *** on its own line (e.g., long notes or cancellation policies)
• Processing time: TripIt usually processes within seconds, occasionally up to a few minutes
• Duplicates: TripIt deduplicates by confirmation number — re-sending updates the existing entry
• Field labels matter: TripIt's parser is strict about label names. This script uses the exact labels from TripIt's official vendor templates. Don't hand-craft emails with different labels (e.g., "Confirmation Number" won't work — it must be "Booking confirmation #")