Label booking mail and drop it on a staff calendar
A CEO's n8n job waits for a human Gmail label, then copies date, vendor and confirmation id onto a side calendar, never the live room book.
Done with
What they did
Staff tag a Gmail thread Events. n8n then lifts date, clock, place, confirmation id, vendor and notes from the body and from PDFs. The body is itself wrapped as a PDF so both streams share one extractor. Attachments win when the two disagree. A new event lands on a side calendar named Auto-imported, with a jump link back to the thread. Blank fields raise a flag instead of a guess. One thread that holds several stays is still a known gap.
How it went
The CEO stopped typing travel confirmations by hand. Multi-stay messages still need a person.
Worth knowing
The Gmail tag is the gate. Untagged junk never reaches the calendar.
For a Pattaya guesthouse
Jomtien desks can tag Booking.com and Agoda mail this way and park arrivals on a staff calendar. Skip a parse fail. Never write onto the live room book.
Set it up
- Make a side calendar for imports. Leave the live room book alone.
- Give staff one Gmail tag for booking mail.
- Lift date, clock, guest or vendor, and confirmation id.
- Write the side-calendar event with a jump link to the thread.
- Ping staff when a field is blank rather than inventing it.
More accounts of this
Read the original via agentusecases.ai
Source: Builder on r/n8n, Reddit ยท 13 May 2026