There are many events that can fire a trigger, and supporting conditions can be added so that the trigger will fire only under the specific circumstances.
"Send Trigger When" vs. "Send Trigger If"
The "Send Trigger When" section contains specific actions or events that will fire a trigger. These include Time Based Events (such as arrival and departure date) or System Events (such as a change to the invoice status.) These events are only true once. In the following example, the trigger would fire when the invoice status changes to paid in full...
The "Only Send Trigger If" section contains supporting conditions that must be true for the trigger to fire, but would not fire a trigger on their own. These conditions are passive, meaning they don't represent a specific event, and will always remain true. They must be paired with a specific event in the "Send Trigger When" section.
In the following example the invoice status must be equal to paid in full for the trigger to fire. Once an invoice is paid in full, it is always paid in full. So this condition must be paired with an event (such as a date based event) for the trigger to fire...
Adding Events to "Send Trigger When"
As you add Events, they will be summarized at the top of this section.
Configure the specifics of the event.
Remove the event.
Add a new event.
Events
This section contains Time Based Events and System Events.
Each event is explained below...
Arrival / Departure Date: This includes Arrival Date Was, Arrival Date Will Be, Departure Date Was, and Departure Date will be. These events reference a specific number of hours/days prior to or after the guests arrival/departure. You can also fire the trigger at check-in. In the example below the trigger will fire one week prior to the guests arrival...
Date: This event will fire the trigger at a specific date in the future. In the example below the trigger is set to fire on June 1, 2023...
Recurring: This allows you to fire a trigger at a set interval, for a set period of time. In the example below the trigger is set to fire on the 1st of every month, from June 1, 2023 through June 1, 2024...
Clean Status: This event will fire the trigger when the Clean Status changes to Clean, Occupied, or Dirty. The following example fires a trigger when the Clean Status changes to "Clean"...
Invoice Payment: This event fires a trigger when the invoice payment is either received or refunded. In the following example, the trigger will fire when a refund is issued on an invoice...
Invoice Status: Probably the most commonly used event, this will fire a trigger when the status of an invoice changes. In the example below, the trigger will fire when the invoice status changes to paid in full...
Owner Block: This event will fire a trigger when an owner block is created or deleted. In the following example, the trigger will fire when an owner block is deleted from the system...
Rental Agreement: Allows you to fire a trigger when the rental agreement is signed, as shown in the following example...
Using Multiple Event Conditions
It is possible to add multiple events to the "Send Trigger When" section of the trigger conditions. Only one event can fire the trigger, so if multiple events are added the trigger would fire if ANY of the events occur. In the following example the trigger will fire if the reservation status is changed to Confirmed OR if the reservation status is changed to Paid in Full...
"Paid" vs "Paid in Full" Status
When collecting a security deposit "at payment of remaining balance", invoices have one additional invoice state. That state is called "Paid", which is different than "Paid-in-Full".
The "Paid" state is triggered when the total payments from the guest meet or exceed the rental charges but not enough has been collected to cover the full security deposit.
You do not want to confuse these two statuses. You should never use the "Paid" status unless you collect security deposits, or your triggers will not fire.