Auto Actions: Difference between revisions
Jump to navigation
Jump to search
| Line 91: | Line 91: | ||
== Examples == | == Examples == | ||
<div class="mw-collapsible mw-collapsed"> | |||
===Automatically change the status of all "Request" bookings to "Cancelled" after three days === | <div class="headline-collapse" > | ||
=== Automatically change the status of all "Request" bookings to "Cancelled" after three days === | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
Trigger tab | Trigger tab | ||
*Trigger Event = After Booking | *Trigger Event = After Booking | ||
| Line 101: | Line 104: | ||
*Execution = One time only | *Execution = One time only | ||
*Booking Status = Cancelled | *Booking Status = Cancelled | ||
</div> | |||
</div> | |||
===Automatically change the status of all bookings which have been imported from Ical to "Request"=== | <div class="mw-collapsible mw-collapsed"> | ||
<div class="headline-collapse" > | |||
=== Automatically change the status of all bookings which have been imported from Ical to "Request" === | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
Trigger tab: | Trigger tab: | ||
*Trigger Event = After Booking | *Trigger Event = After Booking | ||
| Line 113: | Line 122: | ||
Booking changes are applied before the mail is sent. | Booking changes are applied before the mail is sent. | ||
</div> | |||
</div> | |||
<div class="mw-collapsible mw-collapsed"> | |||
<div class="headline-collapse" > | |||
===Automatically set a flag/colour for a booking coming from a certain channel=== | ===Automatically set a flag/colour for a booking coming from a certain channel=== | ||
</div> | |||
<div class="mw-collapsible-content"> | |||
Trigger tab: | Trigger tab: | ||
*Trigger Event = After Booking | *Trigger Event = After Booking | ||
| Line 126: | Line 142: | ||
Booking changes are applied before the mail is sent so that the flag template variable can be reflected in the email. | Booking changes are applied before the mail is sent so that the flag template variable can be reflected in the email. | ||
</div> | |||
</div> | |||
<div class="mw-collapsible mw-collapsed"> | |||
<div class="headline-collapse" > | |||
===Automatically send an Email to the guest when the status of a booking changes to "Cancelled"=== | ===Automatically send an Email to the guest when the status of a booking changes to "Cancelled"=== | ||
</div> | |||
<div class="mw-collapsible-content"> | |||
Trigger tab: | Trigger tab: | ||
*Trigger Event = Check-in | *Trigger Event = Check-in | ||
| Line 141: | Line 164: | ||
<span style="color:#fe746c;“ >{{#fas:exclamation-triangle}} </span> If you are using deposit collection make sure you set SETTINGS->PAYMENTS->PAYMENT COLLECTION "Non Payment Booking Status" = Request. | <span style="color:#fe746c;“ >{{#fas:exclamation-triangle}} </span> If you are using deposit collection make sure you set SETTINGS->PAYMENTS->PAYMENT COLLECTION "Non Payment Booking Status" = Request. | ||
</div> | |||
</div> | |||
<div class="mw-collapsible mw-collapsed"> | |||
<div class="headline-collapse" > | |||
===Automatically change the status of all upcoming direct bookings to "Cancelled" and send an Email to the guest === | ===Automatically change the status of all upcoming direct bookings to "Cancelled" and send an Email to the guest === | ||
</div> | |||
<div class="mw-collapsible-content"> | |||
Trigger tab: | Trigger tab: | ||
*Trigger Event = Check-in | *Trigger Event = Check-in | ||
| Line 155: | Line 185: | ||
*Trigger Action = Auto | *Trigger Action = Auto | ||
*Send Email = Guest | *Send Email = Guest | ||
</div> | |||
</div> | |||
===Automatically add a fee to all bookings from a channel=== | ===Automatically add a fee to all bookings from a channel=== | ||