← Back to library

Parse reservation mail into draft calendar holds

Felix (u/easybits_ai) built this n8n flow after his CEO came back from an event to a pile of flight, hotel and restaurant confirmations. Labeling a message "Events" in Gmail starts it: the flow reads the text and any PDF ticket, creates an entry in a separate import calendar linked to the email, and flags anything that isn't a real booking.

  • OutcomeEvery travel or dinner confirmation you label becomes a calendar entry in its own calendar, with the confirmation number and a link to the original email.
  • SetupUnder an hour
  • LevelIntermediate
  • Creditu/easybits_ai on r/n8n
View original
Works with
n8nChatGPTClaude

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You travel or attend events often and retype bookings into your calendar
  • You want bookings in their own calendar, apart from your main schedule
  • Confirmations arrive from many vendors in different formats

Not for: Bookings that never arrive by email; Shared calendars where an automated event would confuse colleagues

What do you need, and what do you get?

You need

  • A Gmail label you apply to confirmations
  • A dedicated Google Calendar for imported bookings
  • An extraction step that reads both email text and PDF attachments

You get

  • Calendar events with date, time, place, vendor and confirmation number
  • A link from each event back to the source email
  • A review label plus a short notice for mail that wasn't a booking

How does it work, step by step?

  1. Create the trigger labelMake a Gmail label such as Events and get in the habit of applying it to booking mail only.
  2. Extract from body and attachmentsTurn the email text into a document and run it through the same extractor as any attached PDF ticket, asking for the when, where, vendor, booking reference and any notes.
  3. Prefer the attachmentWhen the two disagree, keep the value from the attached ticket; marketing text in the body is less reliable.
  4. Write to a separate calendarCreate the event in a calendar reserved for imports and put the Gmail link in the description.
  5. Catch the mistakesIf required fields are missing, swap the label to Needs-Review and email yourself a list of what couldn't be found.

The prompt

Our own prompt, inspired by u/easybits_ai on r/n8n and written to work in n8n, ChatGPT and Claude. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
Read this booking confirmation. Email text: {email_text}
Attachment text (may be empty): {attachment_text}
Return JSON with: type (flight, hotel, restaurant, event, other), vendor, start_datetime with time zone, end_datetime with time zone, location, confirmation_number, notes. If the attachment and email disagree, use the attachment. If this is not a booking confirmation, return {"is_booking": false, "missing": [list of fields you could not find]}. Never invent a time or confirmation number.

Inspired by u/easybits_ai on r/n8n: Built an n8n workflow that turns any booking confirmation email into a calendar event (flight, hotel, restaurant, etc.). The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Time zones on flights are easy to get wrong; store departure and arrival times with their airport zones.
  • Newsletters from the same vendor get labeled by accident, which is why the review label matters.

Our take

Two design choices make this flow better than the usual "AI reads my inbox" demo. First, a human decides what counts as a booking by applying a label, so the automation never guesses which of a thousand emails matter. Second, the imports go to their own calendar, which means a bad parse is visible and harmless instead of silently moving your real schedule around. The rule that the attached ticket beats the email body is also worth copying: confirmation emails often mention upsells, other dates or promotional offers, and the PDF is the document the airline or hotel actually stands behind. If you adapt it, add a duplicate check on the confirmation number, because many vendors send an update or reminder that would otherwise create a second event. Flights deserve extra care with time zones and overnight arrivals. For a team, the same pattern works for an executive assistant who labels mail on someone else's behalf, as long as the imported calendar is shared read-only.

Where the time goes back: Labeling an email takes a second; building the calendar entry by hand takes a few minutes per booking.

FAQ

Do I need a different parser per airline or hotel?
Felix's point is that you don't: one extraction prompt that asks for the same fields handles any vendor, because it reads meaning rather than layout.
Where is the template?
He published the n8n workflow JSON on GitHub; the link is in his post.

Source and credit

Inspired by u/easybits_ai on r/n8n. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Built an n8n workflow that turns any booking confirmation email into a calendar event (flight, hotel, restaurant, etc.)
Creator
u/easybits_ai on r/n8n
Published on
Reddit
Original date
May 13, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
n8n
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Gate after-hours dental phone triage and booking

Calls are answered and booked against the real schedule, emergencies reach the dentist, and reminders and recalls run without front-desk time.

Credit: u/anassy1 on r/AiAutomations

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Log every agent action as ok, failed or unknown

Give each write an agent makes one structured log line with its attempt ID, request key, an outcome of ok, failed or unknown, and what the agent did next, then keep one saved query for the combination that should never happen, an unknown outcome the agent confirmed to the customer, so a repeat of the incident shows up in minutes.

Credit: ccch713

Under an hour
Operations & AdminWorkflow✓ AI dry run

Pin your agent's write path with one contract test

Build a single fast test workflow that sends the same request key to your agent's booking or order write twice against a stand-in backend, then confirms from an append-only log that exactly one write happened, that the repeat ends as a deliberate skip, and that a forced timeout still lands as unknown and reaches a person, so refactors cannot quietly bring back duplicate writes.

Credit: ccch713

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Run client work on projects, skills and scheduled briefs

Client context that persists, recurring research and reports that arrive on schedule, and meeting prep done before you walk in.

Credit: u/Beginning-Willow-801 on r/ManusOfficial

An afternoon+
Operations & AdminPrompt✓ AI dry run

Stress-test a business decision with an AI pre-mortem

Before committing to a price rise, launch or other big change, have an assistant assume the plan has already gone wrong, rank the likeliest causes with an early signal for each, work out how much loss you can absorb before the change stops paying, list the assumptions underneath with a cheap test for each, and then write the announcement against a scoring rubric it sets first.

Credit: Shubham Vora

Minutes