Automations basics
Build trigger-based message flows that run 24/7 without you touching a thing.
Updated: Apr 10, 2026
Automations are rules that fire when something happens (a booking confirms, a guest checks in, a cleaning finishes). They can send messages, dispatch tasks, generate codes, or call webhooks.
Built-in triggers
reservation_confirmed— fires when a booking is confirmed on any channelpre_checkin— N hours before check-in (default 24h)checkin_day— morning of check-inmid_stay— halfway through stays longer than 3 nightscheckout_day— morning of checkoutpost_checkout— N hours after checkout (default 2h)review_received— when a guest leaves a reviewnoise_alert— when a noise sensor triggers
Your first automation
Go to Automations → New automation. Build this classic flow:
- Trigger:
pre_checkin· 24 hours before - Action: Send email + SMS
- Template:
Hi {{guest_first_name}},
You're checking in tomorrow at {{check_in_time}}.
Address: {{listing_address}}
Door code: {{door_pin}} (valid from 2h before check-in)
WiFi: {{wifi_name}} / {{wifi_password}}
If you're running late, reply here and I'll sort it out.
— {{host_name}}
Shortrental auto-detects the guest's language from their booking and translates the template. You can also write separate templates per language.
Variables available
| Variable | Meaning |
|---|---|
{{guest_first_name}} | Guest first name |
{{listing_name}} | Listing display name |
{{listing_address}} | Full address |
{{check_in_time}} | Scheduled check-in time |
{{check_in_date}} | Check-in date (localized) |
{{door_pin}} | Auto-generated PIN |
{{wifi_name}} {{wifi_password}} | From house manual |
{{host_name}} | Your display name or brand |
Conditions
Add conditions to skip an automation in certain cases:
- Only if channel is Airbnb/Booking/Vrbo/Direct
- Only if stay is longer/shorter than X nights
- Only if guest is a returning guest
- Only if listing is in a specific group
Testing
Every automation has a Test button. It runs the automation against a real upcoming booking of your choice — but sends the output to you instead of the guest. Always test before you activate.
Monitoring
Each automation has an Executions log showing every run, the output, and the outcome (delivered, bounced, etc.). If something looks wrong, click any execution to see the full request/response.