Trip Planner Template

• What it does: Takes trip details (origin, destination, dates) and coordinates three specialist agents: Flight Logistics Manager (SerpApi Google Flights), Tourism Specialist (web search for attractions and hotels), and Hotel Specialist (SerpApi Google Hotels), then the Itinerary Architect consolidates everything into a day-by-day travel plan.
• Best for: travelers, travel agents, teams planning offsites or group trips
• Apps used: SerpApi (Google Flights), SerpApi (Google Hotels), Web Search
• Setup time: 10 to 15 minutes

Trip Planner is a no-code, multi-agent workflow that turns origin, destination, and dates into a full travel plan. The Itinerary Architect coordinates the Flight Logistics Manager (flight options via SerpApi Google Flights), the Tourism Specialist (top attractions and highly-rated hotels via web search), and the Hotel Specialist (hotel options via SerpApi Google Hotels), then assembles a day-by-day itinerary. Flight and hotel APIs require a SerpApi key. This template acts as a starting point: any app, instructions, and agents can be updated as required for your own use case—simply ask Max (Agent Builder) to update the workflow as needed. Last verified from workflow config on March 2026. Includes common failure modes and fixes.

---

Problem this solves

• Planning a trip means juggling flights, hotels, and attractions across many tabs and tools.
• You want one input (route + dates) to get a consolidated plan instead of manual copy-paste.
• Flight and hotel search are standardized (e.g. SerpApi); attractions and recommendations are scattered; you need both in one output.
• A single run that produces a day-by-day itinerary (flights, stays, sights) saves time and keeps the plan in one place.

---

What this agent does

This template can:

• Accept trip details: origin, destination, and dates (and optionally passengers, currency) via the text trigger.
• Use the Flight Logistics Manager with the flight_search_api (SerpApi Google Flights) to search flights and output airline, flight code, departure/arrival times, duration, and price.
• Use the Tourism Specialist with web search to find top tourist attractions and highly-rated hotels (e.g. top 5 attractions, 3 hotels, 4+ stars) with brief descriptions.
• Use the Hotel Specialist with the hotel_search_api (SerpApi Google Hotels) to search hotel options for the destination and dates (check-in/out, adults, etc.).
• Have the Itinerary Architect coordinate all three agents, pass parameters (e.g. currency by origin), and consolidate results into a day-by-day itinerary without inventing information.
• Deliver a single, detailed travel plan (flights, hotels, attractions) for the user.

---

How it works

1. You provide trip details via the text trigger: origin, destination, and dates (e.g. "NYC to Paris, Dec 20–27, 2025"). Include as much detail as possible for accurate results (e.g. outbound_date, return_date, adults, currency).
2. Itinerary Architect receives the input and delegates to three specialist agents, passing the relevant parameters to each.
3. Flight Logistics Manager calls the flight_search_api (SerpApi Google Flights) with origin/destination airport codes and dates; returns airline, flight code, times, duration, price. Parameters (e.g. currency) are set from origin/destination when possible.
4. Tourism Specialist calls web_search_tool to find top 5 tourist attractions and 3 highly-rated hotels (4+ stars) in the destination city with brief descriptions.
5. Hotel Specialist calls the hotel_search_api (SerpApi Google Hotels) with destination, check-in/out dates, and optional adults/children; returns hotel options.
6. Itinerary Architect collects all outputs and assembles a day-by-day itinerary (flights, hotels, attractions). It does not invent data; it only uses what the specialist agents return.
7. You receive the consolidated travel plan in the workflow output.

---

Requirements

• SerpApi key: Required for flight and hotel search. Get a key at serpapi.com. Configure the flight_search_api and hotel_search_api tools with the key (e.g. in params or config).
• Web Search: Enabled by default for the Tourism Specialist; no key needed.
• Input: Origin and destination (airport codes or city names that map to codes), outbound date, return date (YYYY-MM-DD). Optional: adults, children, currency, language/country for search (gl, hl).

---

Setup guide

1. Clone the template and open it in AgentSpace.
2. Enable and configure flight_search_api: In the Flight Logistics Manager’s tool (flight_search_api), enable the tool and set the SerpApi key (e.g. in the api_key parameter). The tool uses SerpApi Google Flights (engine: google_flights); set departure_id, arrival_id, outbound_date, return_date as required.
3. Enable and configure hotel_search_api: In the Hotel Specialist’s tool (hotel_search_api), enable the tool and set the SerpApi key. The tool uses SerpApi Google Hotels (engine: google_hotels); set q (query), check_in_date, check_out_date, and api_key as required.
4. Ensure Web Search is enabled for the Tourism Specialist (default).
5. Run Test Workflow with a sample trip (e.g. "JFK to CDG, 2025-12-20 to 2025-12-27"). Confirm flight options, attractions/hotels from web search, and hotel options from SerpApi, then a consolidated itinerary.
6. Refine trigger input format in the Itinerary Architect instructions if you want specific date/passenger/currency handling.

Common issues and fixes

• No flight or hotel results: verify SerpApi key is set and the tools are enabled. Check airport codes (3-letter, e.g. JFK, CDG) and date format (YYYY-MM-DD). SerpApi rate limits may apply.
• Tourism results generic or missing: web search varies by query; the Itinerary Architect can pass a clearer destination city or "top attractions" phrasing. Adjust the Tourism Specialist instructions if needed.
• Itinerary incomplete or wrong: the Itinerary Architect is instructed not to invent information; it only uses agent outputs. Ensure all three agents run and return data; check tool connections and parameters.
• Currency or locale wrong: set currency (and gl/hl if supported) in the flight and hotel tool params or in the agent instructions (e.g. from origin country).

Customization knobs

• Change number of attractions or hotels (e.g. top 10, 5 hotels) in the Tourism Specialist instructions.
• Add or swap tools (e.g. another flight or hotel API) and update the corresponding agent; keep the Itinerary Architect’s consolidation logic in sync.
• Adjust output format (e.g. by day, by category) in the Itinerary Architect instructions.
• Add a step to save the itinerary to a doc or calendar (e.g. Google Doc, Notion) by adding an agent or tool that writes the final output.

---

Apps used

(SerpApi keys and params are set in the custom_api_endpoint tool config.)

---

Use cases

• Personal trip: One prompt with route and dates to get flights, hotels, and sights in one itinerary. Best for individual travelers.
• Group or offsite: Same flow for team offsites; share the consolidated plan. Best for team leads and admins.
• Travel agents: Quick first draft of a trip plan for clients; edit and extend as needed. Best for agents and planners.
• Recurring trips: Re-run with different dates or destinations for multiple itineraries. Best for frequent travelers.
• Discovery: Use Tourism Specialist output (attractions, hotels) even without flights to explore a destination. Best for research and inspiration.

---

Example prompts and outputs

Example 1: Round trip

Prompt (input): JFK to Paris CDG, outbound 2025-12-20, return 2025-12-27, 2 adults

Output: Flight Logistics Manager returns flight options (airline, code, times, duration, price). Tourism Specialist returns top 5 attractions and 3 hotels (4+ stars) in Paris. Hotel Specialist returns hotel options for the dates. Itinerary Architect consolidates into a day-by-day itinerary (flights, hotels, attractions).

Example 2: One-way or open-ended

Prompt (input): Austin AUS to London LHR, 2026-01-15, 1 adult, currency USD

Output: Same flow; if the flight API supports one-way, you get one-way options; otherwise adjust dates or use return_date same as outbound. Itinerary reflects what the agents return.

Example 3: Focus on attractions only

You can run with minimal dates and rely heavily on Tourism Specialist (and optionally Hotel Specialist) to get attractions and hotels; Flight Logistics can be skipped or run with placeholder dates if you only need destination research.

---

Why you need this template

• One input (origin, destination, dates) produces a full plan: flights, hotels, and attractions in one place.
• Specialist agents keep flight/hotel search (SerpApi) and web research (attractions) in sync with your parameters.
• No invented data: the Itinerary Architect only uses what the agents return.
• Editable in AgentSpace: change agents, add tools, or adjust output format without code.

---

FAQs

1) Do I need a SerpApi key?

Yes, for flight and hotel search. Get a key at serpapi.com and add it to the flight_search_api and hotel_search_api tool configs (e.g. api_key parameter).

2) Can I use other flight or hotel APIs?

Yes. Replace the SerpApi custom_api_endpoint tools with another flight or hotel API (or marketplace app if available); update the Flight Logistics Manager and Hotel Specialist agents to call the new tools and map parameters.

3) What date format does the workflow use?

Use YYYY-MM-DD for outbound_date, return_date, and hotel check_in_date/check_out_date (e.g. 2025-12-20).

4) Why are airport codes required for flights?

The SerpApi Google Flights tool expects departure_id and arrival_id as 3-letter airport codes (e.g. JFK, CDG). The Itinerary Architect or you can pass city names; the Flight Logistics Manager or tool config may need to map city to code if your input is city-only.

5) Does the Itinerary Architect invent information?

No. It is instructed to use only what the Flight, Tourism, and Hotel agents provide. If an agent returns no data, that section of the itinerary will be empty or minimal.

6) What are the main failure modes?

Missing or invalid SerpApi key, wrong or missing airport codes or dates, tools disabled, or rate limits. Fix by checking key, enabling tools, and using valid codes and YYYY-MM-DD dates.

7) Can I save the itinerary to a doc or calendar?

The template returns the itinerary in the workflow output. To save to Google Doc, Notion, or calendar, add an agent or tool that takes the final output and creates a doc or event; connect the Itinerary Architect’s output to that step.

8) How do I add more days or activities?

Adjust the Itinerary Architect instructions to structure the day-by-day plan (e.g. more days, time blocks). The content still comes only from the three specialist agents; you can add placeholder sections or prompts for "things to do" if you add more research agents.

---

Related templates

• Personal Ops AI Assistant – calendar, comms, and retrieval.
• Meeting Schedular – schedule meetings and find slots.
• Pre-Meeting Preparation – meeting briefs with internal and external context.
• Structured Output – structured data for downstream use.
• Marketing Strategy – research and strategy document.