Booking hotels with Claude: one tax-inclusive total per site, reviews mined for hidden fees, deals broken down night by night, then a daily watch for a drop
Efistoffeles(Reddit 用户 u/Efistoffeles,原帖作者本人,自述常出差/旅行订房)Reddit · 2026-10-17
Read originalSaved text / editorial summary
原帖正文(Reddit r/claude,作者 u/Efistoffeles,Atom 源 updated 字段 2026-10-17;本轮经 Reddit 公开 Atom feed 取得,以下为节选,删节处以 … 标出,英文部分逐字未改写): “1. Get one real total per site. … someone booked the cheapest one and then got a bed, tax a resort fee, a destination fee, and a "community impact fee" at the desk. When I looked at a few thousand rates in one city almost half had a fee you pay at the hotel on top, and for the exact same hotel one site showed the city tax and another didn`t, so comparing nightly prices across sites is basically comparing different things. With connectors Claude pulls the same room from a few sites at once and gives me one number per site for the whole stay with every tax and fee in, which by hand is like 20 minutes of tabs and a calculator and I`d still miss one. 2. Have it read the reviews for you. Nobody reads 300 reviews but that`s where the stuff that costs you money is, the $40 a night parking, the $7 a night "safe fee", the minibar fridge with sensors that charged someone at Mandalay Bay $50 just for moving things around in it … I ask Claude to go through the recent reviews and pull out only the money stuff and anything that sounds like overbooking or the place being closed, and it takes it like 2 minutes. 3. Let it do the maths on the deals. I remember … a "third night free" deal and night two was priced way higher than night one plus a 19% destination fee, so the free night was just spread over the other two. On another hotel … 48 different rates that were really only 7 rooms with different names. I get the deals and the room list with Claude and tell it to correctly check the price, including pricing every night separately … 4. After booking let it keep checking. Hotel prices move a lot, I`ve seen the same room go up 60% in a few hours once the cheap rate sold out, but it also goes down too. If I book with free cancellation I always set a scheduled task with Claude so it checks the same room every day until the free cancellation ends and tells me if it got cheaper so I can rebook at the better price. For live prices these are the connectors I use in Claude: Booking.com / Tripadvisor / Brek / LetsFG …” 中文对照:他强调先拿「一个站点一个真实总价」——同站点的城市税有的算有的不算,还有到店才收的度假费、目的地费,跨站点比单晚价基本是在比不同的东西;用连接器让 Claude 同时拉同一间房,给出含全部税费的整段总价。第二步让 Claude 读近期评论,只挑与钱有关的部分和听起来像超售、停业的内容。第三步让它算促销的真实差价,包括逐晚单独计价,并把其实是同一房型的不同报价归并。第四步是订完继续盯:只在可免费取消时订,再设定时任务每天查同一间房直到取消截止,跌了就重订。帖末列出了他在用的四个连接器。
Business model
Reddit user u/Efistoffeles described his four-step hotel routine in r/claude. First, get one real total per site: the same room shows different things on different sites - some include city tax, some do not, and resort, destination or 'community impact' fees are collected at the desk - so he has Claude pull the same room from several sites via connectors and get one tax-inclusive number for the whole stay. Second, let it read the reviews: nobody reads 300 reviews, but that is where the money is - parking at 40 a night, a 7 'safe fee', a minibar with sensors that billed someone for moving things, a family that drove nine hours to a hotel that had been closed for months. He asks Claude to extract only the money items and anything that sounds like overbooking or closure. Third, let it do the maths on deals: his example is someone else's, remembered from Reddit - a 'third night free' where night two was priced far higher plus a 19 percent destination fee, so the free night was simply spread across the other two; and, from a hotel he checked himself, 48 rates that were really only 7 rooms under different names - also his own observation, unverified. Fourth, keep checking after booking: prices move a lot - he has seen the same room go up 60 percent in hours - so he only books free-cancellation rates and sets a scheduled Claude task to check the same room daily until the cancellation window ends and tell him if it got cheaper so he can rebook. No saving total, room rate or tool cost appears in the post. His claim that almost half of a few thousand rates in one city had an at-hotel fee is his own observation, unverified, and the post ends with four connector links, which reads partly as promotion - both disclosed here.
The hard part here is the unit of comparison, not the automation. Nightly rates across sites are not comparable once you account for city tax and at-hotel fees; normalise first, then compare. The second lever is review mining, because the things that actually cost money are buried in reviews nobody reads.
Workflow
- Fix the comparison basis first: whole stay, tax inclusive, at-hotel fees listed separately.
- Pull the same room from a fixed site list; one number per site, each with a capture time. (Site list and connectors follow the original post; the capture-time rule is AgentFlow's.)
- Read reviews for two things only: items that cost extra, and signs of overbooking or closure.
- Break any promotion down night by night and merge rates that are the same room under another name.
- Only book free-cancellation rates, then run a daily check that stops on the cancellation deadline.
- Rebooking and cancelling stay with the person; the agent only flags. (AgentFlow's boundary; the original post does not describe an authorisation limit.)
Adaptation plan
The post gives no saving total, no room rate, no successful rebooking example and no subscription or connector cost. It does not say which sites were pulled for a given stay, how often the daily check actually fired, or whether any flagged drop was ever acted on. The statistics it quotes - almost half of a few thousand rates carrying an at-hotel fee, a 60 percent swing in hours, 48 rates that were really 7 rooms - are the author's own observations with no source given. The four connector links at the end read partly as promotion and no relationship between the author and those services was verified. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run.
Prompt
AgentFlow draft · Untested.
You are my hotel comparison assistant. You may organise prices, read reviews, compute promotions and report price changes by day. You do not book, do not modify or cancel an existing booking, and do not log into my accounts. [INPUT] - Hotel and room: [hotel name], [room and bed type], [check-in and check-out dates] - Sites to compare: [site list] - My basis: total for the whole stay, with tax split into included and payable-at-hotel - If already booked: [total paid], [free cancellation yes/no], [cancellation deadline] [STEPS] 1. Pull the same room and room type from each site and output a table: site / total for the stay / tax included / at-hotel items and amounts / capture time. If a site fails, write not retrieved and say why. 2. Read recent reviews and output only two categories: specific items that cost extra, with amounts and how often they are mentioned; and anything suggesting overbooking, closure or no room on arrival. Output nothing else. 3. If a promotion exists (third night free, stay-three-pay-two), output a night-by-night price table, merge rates that are the same room under a different name, and give the difference between taking and not taking the promotion. 4. If I have booked with free cancellation, run the daily check until the deadline: today's price / difference from what I paid / whether it crossed my threshold / days left before the deadline. [OUTPUT] 1) per-site total table; 2) review extract limited to the two categories; 3) promotion comparison; 4) daily monitoring report including days remaining. [NEEDS MY CONFIRMATION] - Rebooking, cancelling or booking: advice only, I execute. - At-hotel charges the site does not disclose: write not disclosed, never estimate. - If a promotion difference depends on an assumption, state the assumption. [IF MATERIAL IS MISSING OR A STEP FAILS] Blocked site, anti-bot wall, room type mismatch, missing price field: record it as not retrieved with the reason. Do not substitute another site's price and do not reuse yesterday's number as today's. On the cancellation deadline, stop the check and say so explicitly.
Running costs and pitfalls
The post gives no saving total, no room rate, no successful rebooking example and no subscription or connector cost. It does not say which sites were pulled for a given stay, how often the daily check actually fired, or whether any flagged drop was ever acted on. The statistics it quotes - almost half of a few thousand rates carrying an at-hotel fee, a 60 percent swing in hours, 48 rates that were really 7 rooms - are the author's own observations with no source given. The four connector links at the end read partly as promotion and no relationship between the author and those services was verified. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.