← All templates

Short-Term Rental

Short-Let Turnover Dispatch

A short-let turnover fails in the same three ways every time: the cleaner did not know about the same-day check-in, the linen ran out, or nobody noticed the consumables were low until the guest did. This workflow fires on the booking, books the cleaner into a shared calendar with the exact checkout and check-in times, sends the job sheet, and logs the turnover so you can see which property is quietly eating your margin.

6 stepsRequires Zapier Starter or higher25 minMedium
Google CalendarTwilioGoogle SheetsGmailTodoist

What you get

The cleaner sees the checkout time, the next check-in time and the gap between them.
Same-day turnovers are flagged in advance rather than discovered on arrival.
Every turnover is logged per property, so cleaning cost per night stops being a guess.

Workflow blueprint

GC
When this happens
Google CalendarNew Event
1GC
Google CalendarCreate Detailed Event
2TW
TwilioSend SMS
3GS
Google SheetsCreate Spreadsheet Row
4GM
GmailSend Email
5TO
TodoistCreate Task

The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.

Getting it into Zapier

Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 6 steps, so it is a copy-and-paste job rather than a design job.

You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →

Not on Zapier?

n8n — import and go

An n8n workflow JSON ships with this template. Import it and all 6 steps arrive on the canvas wired in order, and 6 of the 6 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Every step maps to a native n8n node.

What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.

Make — build guide

A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.

Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →

Setup steps

1
Detect the new booking

Configure this step using the field mapping in the blueprint.

2
Create the turnover job in the cleaning calendar

Configure this step using the field mapping in the blueprint.

3
Text the cleaner the job details

Configure this step using the field mapping in the blueprint.

4
Log the turnover

Configure this step using the field mapping in the blueprint.

5
Email the job sheet and restock check

Configure this step using the field mapping in the blueprint.

6
Create the guest-review task

Configure this step using the field mapping in the blueprint.

Implementation notes

  • The four-hour window is the entire point of the calendar event. A cleaner who thinks they have all day will find out otherwise on a same-day turnover.
  • Guest reviews expire after fourteen days on Airbnb, and the deadline is invisible in the app until it has passed. That is why the task exists.
  • Log the clean cost per turnover, not per month. Cost per night is the number that tells you which property is actually profitable.
  • Above roughly six properties, replace the individual SMS with a shared cleaner calendar and let them self-assign. Personal texts stop scaling around then.