TravCozy

All your trips in one place

Category: Pending
Primary Subcategory: Pending

Integration details

Description

TravCozy keeps every part of your trip together. Ask ChatGPT about your travels and it answers from your real bookings — flights, hotels, trains, car rentals, and transfers imported from any booking site — organized into a day-by-day itinerary. It also spots what's missing before you travel: nights without accommodation and arrivals with no onward transport. Add bookings right from the conversation by describing them, by uploading a confirmation file, or by forwarding booking emails to your TravCozy inbox — they're organized into the right trip automatically. Requires a TravCozy account (travcozy.com).

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-09-03
Tool count: 18
Geography: US

ChatGPT Plugin Discovery Score

ChatGPT Plugin discovery is coming soon

ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.

No spam. Unsubscribe any time.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce TravCozy has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

18 tools agents can invoke

MANUALLY add/create a hotel stay, flight, train, car rental or transfer on a trip from details given in chat — no document or confirmation needed. Use this whenever the user wants to add a booking by hand ("add the Ritz-Carlton Warsaw Aug 30 – Sep 1", "I'm flying LO 281 on Friday"). Dates the user actually stated are required; never guess missing dates — ask.
add_booking
Create a new empty trip. Use only when the user explicitly wants a trip without a booking — imported bookings create/match trips automatically.
create_trip
Delete a booking AND its segments. Restorable for 30 days (restore_deleted). Flight alerts/status history on deleted flight segments are lost (alerts re-arm if restored). Requires expected_updated_at of the booking.
delete_booking
Delete one segment. Restorable for 30 days (restore_deleted). For flight segments, active flight alerts and status history on the segment are lost (alerts re-arm automatically if restored). Requires expected_updated_at.
delete_segment
Delete an ENTIRE trip with all bookings and segments. Requires confirm_title matching the trip's exact title AND expected_updated_at. Sharing links die permanently (not restored); flight alerts/status history are lost; trip+bookings+segments are restorable for 30 days.
delete_trip
How to add bookings to TravCozy hands-free by forwarding confirmation emails. Call this when the user asks how to import bookings, or suggest it after adding a booking manually — forwarding is the zero-effort path.
get_import_guide
Full detail of one trip: bookings with their nested segments (flights, hotels, trains, car rentals, transfers) plus unattached segments, and the day-by-day `timeline` grouping (identical to the TravCozy app's timeline). status is derived from the dates.
get_trip
Import a booking confirmation the user pasted or attached in chat (email text, PDF, or image/screenshot). TravCozy extracts the booking, matches it to the right trip by travel dates (or creates one), and stores it. Prefer this over add_booking whenever a document exists.
upload_booking
List the user's trips with dates, destination, status and per-type segment counts. status is derived from the dates: upcoming | active | completed | cancelled. scope: 'upcoming' (default) = trips not yet ended, 'past' = ended, 'all'.
list_trips
Move a booking (with all its segments) to another trip. Requires expected_updated_at of the booking.
move_booking
Move an unattached segment to another trip (segments inside a booking move with their booking — use move_booking). Requires expected_updated_at of the segment.
move_segment
Restore a delete made in the last 30 days, using the restore_group returned by the delete. Restores trips/bookings/segments with their original ids. NOT restored: sharing links (recreate deliberately), weather cache (refetches), notifications, flight status history (alerts re-arm automatically).
restore_deleted
Search trips by free-text query (title/destination), destination, and/or date-range overlap. Same row shape as list_trips.
search_trips
Find what's MISSING from a trip: nights with no accommodation booked, and arrivals (flight/train) with no onward transport within 4 hours. Includes cached weather for the trip days when available. Use this to proactively help the user complete their trip.
get_trip_gaps
The next N days of travel events across ALL trips, sorted — the "when is my flight?" tool. Events: flight/train departures, hotel check-ins, car and transfer pickups.
get_upcoming
Update booking-level fields (confirmation number, price, currency, source, passenger, notes) — not its segments. Requires expected_updated_at from a fresh read.
update_booking
Update one segment's fields (times, locations, names, prices, notes). segment_type: flight | hotel | car | train | transfer. Datetimes are LOCAL wall-clock "YYYY-MM-DDTHH:mm" — never converted. Requires expected_updated_at from a fresh read.
update_segment
Update a trip's own fields (title, destination, dates, type, status). Pass fit_dates:true instead of start/end to auto-fit the dates to the trip's segments. Requires expected_updated_at from a fresh read.
update_trip

TravCozy FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.