Hey n8n Community,
My CEO came back from a conference last week and asked me for help with a problem I bet a lot of you can relate to.
He attends a lot of events, which means his inbox gets flooded with booking confirmations – flights, hotels, restaurants, event tickets. And someone (usually him) has to manually add all of that to his calendar.
The kicker: he wanted these appointments in a separate calendar so his main schedule stays clean. Manually creating each event was eating up time that should’ve gone to actual work.
So I built this:
How it works
- You label any confirmation email in Gmail with “Events”
- The workflow extracts date, time, location, confirmation number, vendor, and notes from both the email body and any PDF attachments
- A calendar event lands in a dedicated “Auto-imported” Google Calendar with all the details and a link back to the original email
- Non-confirmations (newsletters that got accidentally labeled) get flagged with a “Needs-Review” label and you get a notification email listing what was missing
What makes it work for any vendor
One easybits Extractor pipeline handles every format – Lufthansa, Booking, OpenTable, your dentist, DHL, whatever. No per-vendor parsing logic. The email body gets wrapped into a PDF and extracted in parallel with any PDF attachments, then the two results get merged (attachment data wins because the attached ticket is more authoritative than promotional email body text).
Free workflow template + JSON
Does anyone else have a similar problem with calendar clutter from business travel? Curious what other email-to-calendar use cases people are dealing with.
Best,
Felix
2 個讚
Hotel confirmations are the thin ones in that pipeline, a flight email hands you flight number, terminal, gate and times, a hotel email often gives you a property name, a check-in date and a booking ref and not a lot else, so those calendar events come out sparse compared to the flights, and half the time the address only lives in the PDF, which is why your attachment-wins merge matters more for hotels than anything else. Where I’d take it next is enrich the hotel events after extraction, you already have the property name and dates, so hit a data API with those and pull the address, check-in time and phone into the event, and the nightly rate if the CEO’s expensing it, that’s a data lookup rather than more extraction. I build one for that (StayingAPI, Airbnb, Booking, Vrbo and Google Hotels, so it does the hotel leg and nothing else in your list), so weigh that accordingly, but it’s the piece the email itself can’t give you.
Hey @paperandbeyond23-gif, first of all, thank you so much for the feedback! I really like the idea of enriching hotel events with another API. Would you be open to collaborating on a workflow that builds on my booking-to-calendar workflow and integrates your API as well?
I’ll also send you a DM so we can discuss it further.
The hotel leg is the thin one because a confirmation email gives you a property name and dates and not much else, so enrichment has to come from a lookup rather than better extraction. The name is where it gets awkward: the email spells the property the way that hotel’s marketing spells it, and most hotel APIs key on their own property id, so you are either matching first or you need a lookup that takes the name as written. That second shape is the one worth knowing about. Live nightly rate for the property and the dates you already extracted, with the property it matched echoed back so a wrong match is visible instead of silent. That is also what makes the expense case work. We sell that API and we maintain a community node for it, n8n-nodes-flightpowers, flights and hotels.
1 個讚
Hey @mtnrabi, thank you for the feedback! I really like the idea of pulling real-time data from hotels, and I’ve actually already been in touch with the people at StayAPI (https://stayapi.com/). They also provide an API that allows you to pull live data from all the major travel sites.
What I’d be interested to understand is what sets Flight Powers apart from StayAPI. Is there a significant difference in the data you can get from it, or would I essentially get the same data from both?
Hi Felix, fair question, and the honest answer is they overlap on Booking.com and not much else.
Where StayAPI is ahead: 18 sources (Expedia, Agoda, Airbnb, TripAdvisor and several chain sites), reviews with topic scores, and room-level detail like refundable-until and rooms left. If your workflow needs that breadth, they cover more.
Where FlightPowers is ahead:
- Flights. They have none. One call takes a date range and a list of destinations and returns every fare with Google’s own low/typical/high verdict, round trips priced as one request.
- Booking.com search with 24 filters (review score, stars, meal plan, free cancellation, pool, pets and so on) plus a budget-per-night cap. Their Booking search has no filters and needs a second billed call to resolve the destination id first.
- Lookup by property name for the hotel and dates you parsed out of the email, with the matched property echoed back so a wrong match is visible instead of silent.
- Rate as seen from a given country (proxy_country), which I haven’t seen documented elsewhere.
- Price: their Basic is $49 for 1,500 requests. Ours is $10 for 2,000 hotel or 2,500 flight requests, self-serve on RapidAPI, with a free tier to try.
The n8n node is n8n-nodes-flightpowers, flights and hotels behind one credential. Docs: API docs: flights and hotels, endpoint by endpoint · FlightPowers
For the calendar-event case, is it the rate you want on the event, or the reviews?
