Docs / Plan with AI
Let an AI draft the route. You make it yours.
Any chat assistant can sketch a road trip in a minute. Give it our prompt, tell it where you want to go — in your own language — and paste its answer into Routebook: days, stops and overnights on the map, ready to drag around.
Copy the prompt
Start a new chat and paste this in first. It tells the assistant what to ask you and exactly how to write the answer. You don’t need to read it — just copy it.
You are helping me plan a road trip for Routebook, a road-trip planner.
Talk to me in the language I write in. In the file, keep the keys,
stop_type values and place names in English, exactly like the example
below; day labels and notes can be in my language.
First, ask me anything you still need: start and end point, dates, how many
hours I like to drive per day, who's coming, what we enjoy. Suggest a plan
in plain words and let me change it.
When I say "make the file", reply with ONE json code block and nothing
else, in exactly this shape (the values are only an example):
```json
{
"version": 1,
"name": "Munich to Lake Garda",
"starts_on": "2027-06-12",
"ends_on": "2027-06-13",
"avoid_highways": false,
"avoid_tolls": false,
"prefer_scenic": true,
"days": [
{
"label": "Over the Brenner",
"day_index": 1,
"start_minutes": 540,
"stops": [
{ "name": "Munich, Germany", "stop_type": "start" },
{ "name": "Innsbruck, Austria", "stop_type": "visit",
"stay_minutes": 90, "notes": "Old town and the Golden Roof" },
{ "name": "Bolzano, Italy", "stop_type": "overnight",
"notes": "Book near the centre, parking is tight" }
]
},
{
"label": "Down to the lake",
"day_index": 2,
"start_minutes": 570,
"stops": [
{ "name": "Trento, Italy", "stop_type": "drive_through" },
{ "name": "Riva del Garda, Italy", "stop_type": "overnight" }
]
}
]
}
```
Rules for the file:
- One entry in "days" per driving day, day_index counting from 1.
- stop_type is one of: start, visit, drive_through, overnight.
- Day 1 opens with a "start" stop. Every day but the last ends with an
"overnight" stop; the next day continues from there, so don't repeat it.
- Name every stop the way a map search finds it, with the region or
country: "Hallstatt, Austria", never "the lake village".
- start_minutes is when the day starts, in minutes after midnight
(480 = 8:00, 540 = 9:00).
- stay_minutes is how long we stop at a "visit", in minutes.
- Dates are YYYY-MM-DD. Use null for starts_on and ends_on if I haven't
picked dates.
- Put tips, bookings and warnings in "notes", not in new fields.
- Do NOT add lat or lng. Routebook looks every place up itself.Why no coordinates? Chat assistants are good at picking places and bad at remembering exactly where they are — a guessed coordinate can land you in the wrong valley. Routebook looks each name up on the map instead.
Describe your trip
Brief it like a friend who knows the area, in whatever language you like. Answer its questions, push back on anything you don’t like, and only say “make the file” once the plan reads right.
For example, you write
Eight days in June, Munich to Lake Garda and back, through the Dolomites. Two adults and a dog. Max four hours of driving a day, we’d rather take the pretty road. We like short hikes and good food, not museums.
It asks before it plans
Lovely route. Two quick things first: are you happy to go over the Brenner, or should I avoid motorway tolls? And would you like two nights at the lake instead of one?
Then, once it’s right
Looks good — make the file.
Your language, its format. Chat in any language you like. The prompt asks the assistant to keep the file’s keys and place names in English, the way Routebook reads them; day labels and notes come out in your language. You won’t have to touch it.
Worth mentioning
- Start and finish. A round trip, or one-way?
- Dates or length. Exact dates fill in the calendar; “ten days” is fine too.
- Driving per day. The single biggest lever on how the days split.
- Roads to skip. Motorways, toll roads, or “scenic wherever possible”.
- Must-sees. Anything already booked, so it plans around it.
Paste it into Routebook
No file to save. Copy the assistant’s reply — the whole thing is fine — and paste it in.
- Copy the reply. Most assistants put a copy button on the code block; copying the whole message works just as well.
- On Your trips, choose Import from AI, then Paste from clipboard. A .json file works too — pick it or drop it on the box.
- Check the preview — name, days, stops — and choose Create trip. Routebook finds every place on the map and opens the trip.
Rework a trip with AI
Hand a trip you planned in Routebook to an assistant — to add a rest day, swap the route, or find somewhere to stay — and take the answer back.
- Open the trip, open Trip actions (the ⋯ button) and choose Rework with AI. It shows a prompt with your trip already inside — press Copy prompt.
- Paste it into a new chat and say what should change: a rest day, no toll roads, a shorter day 3.
- Copy the answer, go back to the same sheet (or Import trip data in the menu), press Paste the answer, and pick Replace this trip — or Create new trip to keep both.
The file, field by field
You never have to write this by hand, but it helps to know what you’re looking at. It’s the same format Export › Trip data saves.
| Field | Needed | What it does |
|---|---|---|
| version | Optional | Always 1. Assumed when left out. |
| name | Yes | The trip’s title. |
| starts_on · ends_on | Optional | Dates as 2027-06-12, or null. |
| avoid_highways · avoid_tolls | Optional | true or false for the whole trip. False when left out. |
| prefer_scenic | Optional | Favour the slower, prettier road. |
| days[] | Yes | At least one. Each has a label, a day_index, an optional start_minutes (540 = 9:00) and its stops. |
| stops[].name | Yes | What Routebook searches the map for. Be specific: town and country. |
| stops[].stop_type | Optional | start visit drive_through overnight. Visit when left out. |
| stops[].stay_minutes | Optional | Time spent at a visit. 75 minutes when left out. |
| stops[].notes | Optional | Free text on the stop — tips, bookings, parking. |
| stops[].lat · lng | Optional | Both or neither. Leave them out for AI-made trips; exported trips keep them. |
When something’s off
- Not found on the map
A stop didn’t make it in
Its name was too vague to find. The import lists which ones — add them from the search bar, or ask the AI for fuller names with the region or country, and import again.
- Invalid JSON
The reply won’t read
Usually the answer was cut off mid-file. Ask the AI to “send the whole file again, only the json”. Text around the code block is fine — Routebook skips it.
- Day 2, stop 3 …
A field is the wrong type
The message names the day, stop and field. Press “Copy a fix request for your AI”, paste it into the chat, and paste the corrected answer back.
- Drive times
A day runs longer than promised
The AI estimates; Routebook measures the real roads. Trust the planner’s numbers, and drag a stop to the next day if one runs long.
It’s a first draft, not a verdict.
Once it’s in, the trip is yours: drag stops between days, check fuel and budget, and share it with whoever’s riding along.