Changes

Jump to navigation Jump to search

Auto Actions

11 bytes added, 08:40, 23 May 2020
no edit summary
[[Category:Troubleshooting]]
[[Category:Automation]]
[[Category:Webhooks]]
<div class="heading">Auto Actions</div>
This page is about the menu {{#fas:cog}} (SETTINGS -> ) GUEST MANAGEMENT -> AUTO ACTIONS and explains how to set up and use Auto Actions.
An Auto Action is an action which can be programmed to occur at a time relative to the time the booking was made, to the check in date or to the check out date. To use this function you need to set the system to use you own Email address for sending in SETTINGS->ACCOUNT->OUTGOING EMAIL.
== Test ==
Test why an auto action did not trigger.
 
== Troubleshooting ==
'''If Auto Actions do not send:'''
The list in the "Mail" tab of the booking will tell you why. Common causes are:
*Is your outgoing Email address working? Go to SETTINGS->ACCOUNT->OUTGOING EMAIL and click on "Send Test Email".
*Is your Auto Action set to send automatically?
*Is the guests Email address valid ("Mails" tab of the booking)?
*Is the booking set to allow Allow Auto Actions ("Mails" tab of the booking)?
*Do all trigger events apply to the booking?
 
'''Auto Action is not editable'''
To have write access to an auto action an account needs to have write access to all properties to which the auto action applies. This might not be the case if you use sub accounts and the Auto Action is set to trigger for "All Properties".
 
'''You don't have permission to access control2.php on this server''' error message, when the save button is clicked
It is most likely something in your content triggering the firewall.
Try adding the content bit by bit until you find the item causing the problem.
Often it is a script or HTML item that appears to the firewall as a possible hacking attack.
It can also be something that looks innocent like a combination of numbers and words like "and" or "or" that hackers often use in sql injection attacks.
Once you find the item causing the problem, try rewording it.
<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 mw-collapsed">
<div class="headline-collapse" >  
===Automatically set a flag/colour for a booking coming from a certain channel===
</div>
<div class="mw-collapsible mw-collapsed">
<div class="headline-collapse" >
====Example: Credit card is collected at time of booking and full payment is due 3 days prior to arrival.====
</div>
<div class="mw-collapsible-content">
<div class="mw-collapsible mw-collapsed">
<div class="headline-collapse" >
====Example: Credit card is collected at time of booking and you want to 'Capture' a Security Deposit.====
</div>
<div class="mw-collapsible-content">
</div>
</div>
 
== Troubleshooting ==
'''If Auto Actions do not send:'''
The list in the "Mail" tab of the booking will tell you why. Common causes are:
*Is your outgoing Email address working? Go to SETTINGS->ACCOUNT->OUTGOING EMAIL and click on "Send Test Email".
*Is your Auto Action set to send automatically?
*Is the guests Email address valid ("Mails" tab of the booking)?
*Is the booking set to allow Allow Auto Actions ("Mails" tab of the booking)?
*Do all trigger events apply to the booking?
 
'''Auto Action is not editable'''
To have write access to an auto action an account needs to have write access to all properties to which the auto action applies. This might not be the case if you use sub accounts and the Auto Action is set to trigger for "All Properties".
 
'''You don't have permission to access control2.php on this server''' error message, when the save button is clicked
It is most likely something in your content triggering the firewall.
Try adding the content bit by bit until you find the item causing the problem.
Often it is a script or HTML item that appears to the firewall as a possible hacking attack.
It can also be something that looks innocent like a combination of numbers and words like "and" or "or" that hackers often use in sql injection attacks.
Once you find the item causing the problem, try rewording it.

Navigation menu