STR operations

Give Claude your cleaner rules through the Hospitable connector and let a daily scheduled task check the next four weeks of cleanings, flag any day your main cleaner is booked at two locations, and propose moving the second job to the backup cleaner for your approval

Bill of Double Rainbow Suites, a short-term rental host whose main cleaner can handle only one location per day, posted in the Hospitable Community's MCP Builders group about catching the cleaner double-booked at two locations on the same checkout day more than once. The host's rule: the primary cleaner always gets the pool house first, is never booked at two locations on one day, and on a conflict keeps the pool house while the other job goes to the backup cleaner; the units in the host's other building count as one location, so several cleanings there on one day are not a conflict. Hospitable's built-in task rules assign a cleaner per property but, as far as the host knows, cannot apply conditional logic like that, so the host used Claude with the Hospitable connector. Claude pulled the teammates, properties, and the next four weeks of cleaning tasks, confirmed it could reassign tasks between teammates, checked the current schedule against the rules, and created a scheduled task that runs every morning, groups the multi-unit building as one location, and proposes a swap for each conflict. For the first four weeks every swap waits for the host's approval through a push notification, with a reminder to decide after the trial whether Claude may reassign on its own and report the changes. In a reply, Hospitable Hero Tom Beerley describes similar scheduled calendar sweeps that warn when one cleaner has too many assignments in a day and block nights when no cleaner is available for a same-day turnover.

At a glance

Tools used
ClaudeHospitableMCP
Category
STR operations
Audience
STR host, property manager
Difficulty
No-code setup
Source
Automating cleaner conflict rules in Hospitable with Claude
Double Rainbow Suites (Hospitable Community) · Forum post · Nov 8, 2026
First step
Connect Hospitable to Claude, write your cleaner rules in plain sentences (who gets priority, which units count as one location, who the backup cleaner is), and ask Claude to check the next four weeks of cleaning tasks against those rules before creating any scheduled task.

Compliance note: Keep approval on for every reassignment until the daily check has run correctly for several weeks, and confirm each swap with the backup cleaner so a turnover is never left unassigned.

Suggested prompt

Written by this directory, inspired by the source. Replace the [bracketed] parts.

Using my Hospitable account, pull my teammates, my properties, and every cleaning task for the next 4 weeks. Confirm whether you can reassign a cleaning task from one teammate to another.

My rules: [primary cleaner] always gets [priority property] first. [Primary cleaner] is never booked at two different locations on the same day. [Units in building] count as one location, so several cleanings there on one day are not a conflict. When there is a conflict, [primary cleaner] keeps [priority property] and the other cleaning goes to [backup cleaner].

Check the current schedule against these rules and list every conflict with the date, both properties, and the swap you propose. Then create a scheduled task that runs every morning, checks the next 4 weeks of cleanings against the same rules, and asks for my approval before reassigning any task. Do not reassign anything without my yes.

Share on X Read the source

← All use cases