An Auto Action runs one or more actions on a booking when its trigger conditions are met, either automatically or when you start it manually. Use Auto Actions to send emails, messages or SMS, change booking or invoice information, and run webhooks, at a time relative to the booking, check-in or check-out. You manage them in Settings > Guest Management > Auto Actions.
Table of Contents
- How Auto Actions work
- Create and manage Auto Actions
- Trigger settings
- Actions
- Same-day and near-term bookings
- Multiple properties
- Smart logic template variables
- Performance and testing
- Troubleshooting
- Examples by use case
How Auto Actions work
Each Auto Action has one or more trigger conditions and one or more actions. Triggers can be based on property, time or booking conditions. An Auto Action can:
- send pre-drafted emails, messages or SMS
- change booking information
- change invoice information
- run webhooks
- trigger HTTP POST notifications
You can chain Auto Actions to automate whole workflows.
Use Template Variables so one Auto Action works for several or all properties and rooms, with the property-specific details filled in. You then only need to update one Auto Action instead of editing a copy per property. If the message or purpose needs to differ between properties, use group keywords in the trigger to include or exclude properties.
Note: Auto Actions aren't real-time. They're processed in batches, so allow for this when you set your triggers.
Create and manage Auto Actions
Steps:
- Go to Settings > Guest Management > Auto Actions.
- Click Add New Action.
- Start with an empty Auto Action, or choose a template and customise it.
- Choose how the Auto Action is triggered (see the table below), set the trigger and actions, and click Save.
| Trigger Action | What happens |
|---|---|
| Manual | You trigger the action manually from the Mail & Actions tab of each booking. |
| Auto | The action triggers automatically on bookings that match the rules on the Trigger tab. The Mail & Actions tab of each booking shows whether and when the Auto Action triggered, or whether and when it's due to trigger. |
| To | Do this |
|---|---|
| Change an Auto Action | Click Edit on the Auto Action, make the changes and click Save. |
| Copy an Auto Action | Click Edit, scroll to the bottom of the page and click Save as copy. |
| Delete an Auto Action | Click Edit, scroll to the bottom of the page and click Delete. |
The Auto Actions appear on the Mail & Actions tab of each booking, where you can also trigger emails, messages and booking changes manually.
Set up outgoing email
To send emails with Auto Actions, connect your own email address first.
Prerequisites: your email address is set up in Settings > Account > Outgoing Email. Follow the instructions there to connect your email account to Beds24.
| Sending | Sent from |
|---|---|
| Automatic | The email address of the account that created the Auto Action, as set up in Settings > Account > Outgoing Email. |
| Manual (Send now) | The email address of the user you're logged in as. |
- Confirmation emails are sent to the guest automatically. You can customise them in Settings > Guest Management > Confirmation Messages.
- If you use your own mail server for outgoing emails and messages, booking and invoice actions are applied before the email is sent.
Auto Actions and sub-accounts
Auto Actions apply per account.
- In the account where the Auto Action was created (master account or sub-account), it's available according to the Property setting on the Trigger tab: a specific property or group of properties, all properties owned by the account, or all properties visible in the account (owned and made available to it).
- In another account (master account or sub-account), it's only available for properties that belong to the first account and have been made available in the other account.
To copy an Auto Action to another account, use the clone function: click the user icon at the top right, then Account Management (in the old control panel: Sub Account at the top right). The clone is an independent Auto Action that you can change in the other account.
Tip: To use one Auto Action across several accounts and properties, create it in the master account, set Property to All visible in account, and make sure the master account has access to the properties.
Trigger settings
The Trigger tab sets the conditions a booking must meet before the Auto Action starts.
| Setting group | What it does |
|---|---|
| Property, Room, Unit | Trigger on All properties, All Owned by, All visible in account or a specific property. For a specific property you can also select a room ID. You can exclude specific room IDs (find the room ID in the room setup) and select specific offers or units in room types. Send/Exclude Property Groups uses the group keywords from Settings > Booking Engine > Multi Booking Page > Property Settings > Group Keywords. |
| Time | Trigger Time and Trigger Event set when the action is allowed to start. Once started, it can run for the Time Window period, then it stops. Trigger Time and Time Window are both relative to the Trigger Event: check-in, check-out or time of booking. Use Between Booking and Check in (number of days) to include or exclude same-day and near-term bookings. Use Check In From and Check In To for information that only applies to bookings between those dates, for example special offers or major disruptions. |
| Booking Source | Direct applies the Auto Action only to bookings from your own website, manually added bookings and bookings imported through the API (not the channel manager). To trigger only on manually added bookings, add your username in the Referrer field. |
| Booking Conditions | Group Booking Trigger: see the (?) context help for the options. Invoice Balance: use it for payments and reminders. |
| Info Codes | If you use booking info codes, enter values to include or exclude bookings. |
| Booking Fields | Select fields from the drop-down lists, with an AND/OR option. You can use template variables in the fields to create dynamic values from the booking, see Template variable logic and calculations. |
Actions
Each tab of the Auto Action adds a type of action. You can combine several actions in one Auto Action.
Messages and emails
Create or change a prepared email or message template on the Message tab. Templates can contain Template Variables for booking-specific information, for example the guest's name or the arrival date.
- For messages sent through the Message API, enter the text in the plain text box. For emails, enter the text in the HTML box.
- To send emails automatically, set up your outgoing email address in Settings > Account > Outgoing Email.
- To send an email manually, open the booking and go to the Mail & Actions tab. The email opens in a window, where you can send it as it is or edit it first.
| Sending | How it's sent |
|---|---|
| Automatic | Through your email server. You can see it on your server; whether it shows in your Sent folder depends on your email program. |
| Manual, from the email templates list in the booking | Beds24 first tries to send through your email server (as above). If that doesn't work, the email opens and is sent from your desktop email program, and you see it in your Sent folder. |
Some systems limit this kind of email to about 2,000 characters. If the email doesn't open, try shortening the text.
Email attachments: you can attach an invoice or a booking template as a PDF. Other files can't be attached. Instead, add a link to a file you upload to your website.
Note: Channels may block PDF attachments sent to the alias email addresses they create, so the guest doesn't receive them. Ask your channel about their policy.
HTML and templates: make sure your HTML code is correct and clean, otherwise it might trigger the Beds24 firewall. HTML created by third-party services is often convoluted and can contain critical content. Template tools such as Stripo and Designed with BEE have been tested to work well in Beds24.
SMS
You can send SMS messages automatically. A fee per SMS applies when this function is activated.
- SMS can only be used for information about a current booking. For legal reasons, you can't use SMS for marketing, including discounts or vouchers.
- SMS are sent in the language of the account, not the language of the booking. To control the language, see the example Send SMS in a certain language.
Booking
Use the Booking tab to change something in the booking. Execution sets whether the action runs One time only (default) or Allow Repeats within the trigger period.
Note: Emails are always sent once only, whatever the Execution setting.
Booking Info
Add or remove booking info codes automatically. Info codes are useful for reporting and for including or excluding bookings in other Auto Actions, so you can run Auto Actions in sequence.
For example, an Auto Action that adds a pending payment for a security deposit authorisation should only trigger when the booking info code is STRIPEPAYMENT or CARDTOSTRIPE, which both confirm that the guest's credit card is in the booking.
Invoice
- Assign an invoice number automatically.
- Add or update invoice items or pending payments automatically. Pending payments can use the payment rules from Settings > Payments > Payment Rules.
- Invoice changes are applied before the email is sent.
API and Webhook
Create Auto Actions that send HTTP POST notifications (API) or trigger a webhook when the trigger conditions are met.
Same-day and near-term bookings
If you send the guest several messages at different times before arrival, consider sending one combined message for same-day and near-term bookings. Use Between Booking and Check in on the Trigger tab to control which bookings each Auto Action triggers on.
Same-day bookings: create one Auto Action for same-day bookings with these Trigger tab settings:
| Setting | Value |
|---|---|
| Trigger Event | Booking |
| Trigger Time | Immediate |
| Between Booking and Check in | 0 and 0 (same day) |
In your other Auto Actions, set Between Booking and Check in to 1 and 999, so they don't trigger on same-day bookings.
Near-term bookings: if you send a confirmation message at booking and check-in instructions 2 days before arrival, one Auto Action can cover bookings made 0–2 days before arrival:
| Setting | Value |
|---|---|
| Trigger Event | Booking |
| Trigger Time | Immediate |
| Between Booking and Check in | 0 and 2 (near term) |
On the Message tab, combine the text of your standard confirmation message and your check-in instructions. In your other Auto Actions, set Between Booking and Check in to 3 and 999, so they don't trigger on near-term bookings.
Multiple properties
With several properties, use template variables for the property-specific information in messages to guests, housekeeping or owners. One Auto Action can then send the booking dates, property details and contact details for all or selected properties, instead of one Auto Action per property.
- The property setup is available through property template variables, for example
[PROPERTYNAME](property name) and[PROPERTYADDRESS](property address) from Settings > Properties > Description. - Settings > Properties > Description > Property Templates holds extra property templates with your own text per property. You can use them in Auto Actions, booking templates, invoices and reports.
- Each room or unit has its own room template variables.
See the full lists of property, room and other variables in Template Variables.
Different door code per property: enter the building access code in Settings > Properties > Description > Property Templates > Property Template 1 of each property. In the Auto Action text, use [PROPERTYTEMPLATE1] instead of the code, for example: "Please use this code to access the main building door: [PROPERTYTEMPLATE1]". You don't need a separate Auto Action per property.
Different housekeeping team per property: enter the team's email address in Property Template 5 of each property. In the Auto Action, set Send Message to Internal Only and Internal Email Address to [PROPERTYTEMPLATE5]. The booking details are then sent to the right team for each booking. If you have different teams per room, use a room template instead.
Send to a group of properties: property groups let you include or exclude a group of properties in messages and emails, and view a group in the calendar and reports.
- Go to Settings > Booking Engine > Multi Booking Page > Property Settings > Group Keywords.
- Enter a group name as a single word, for example
4BEDSfor all 4-bedroom properties. A property can be in several groups: separate the keywords with commas, for example4BEDS, OceanView, Dublin. - On the Trigger tab of the Auto Action, enter the keyword in Send Only To Property Groups or Exclude Property Groups.
Note: The group filter doesn't apply when the Auto Action triggers on a single property.
Smart logic template variables
Use smart logic template variables to trigger Auto Actions only under specific conditions, for example on a certain day of the week. %u is the ISO-8601 day of the week, from 1 (Monday) to 7 (Sunday).
| Use | Template variable |
|---|---|
| Remind guests to put the bin out on Wednesday night: test whether today is a Wednesday | [IF=:[CURRENTDATE:{%u}]:3:yes|no] |
| Remind guests that the cleaner comes on Friday morning: test whether today is a Thursday | [IF=:[CURRENTDATE:{%u}]:4:yes|no] |
For all IF variables and operators, see Template variable logic and calculations.
Performance and testing
An Auto Action tests up to 1,000 bookings per cycle. If more bookings match the trigger, the next 1,000 are tested in the next cycle, and so on. For the fastest processing, design the trigger to test fewer than 1,000 bookings: keep the time window as short as possible and use the most specific trigger condition. For example, a trigger that tests all bookings from booking time for one year tests many more bookings, and runs slower, than one that tests only the 7 days before check-in.
- Test tab: a button shows how many and which bookings the Auto Action tests. The list can include bookings that won't trigger it. To check a specific booking, enter the booking number: the test shows whether the Auto Action would trigger, with diagnostic information.
- In the booking: open the Mail & Actions tab, find the Auto Action ID and check the Status column.
One Auto Action can do several things at once: send an email or API message, send an SMS, update booking settings, add or delete a booking info code, trigger a webhook, add a pending payment, add, update or delete a charge or payment item, and assign an invoice number. You don't need a separate Auto Action for each action if they can all apply at the same time.
Note: You can't set an exact time for an Auto Action to trigger. A trigger time of Immediate + 14 hours, for example, doesn't trigger at 2 pm local time. It's the earliest time the booking is checked against the other conditions and added to the batch for processing.
Troubleshooting
| Problem | Solution |
|---|---|
| Auto Action doesn't send |
The list on the Mail & Actions tab of the booking shows why. Common causes:
|
| Auto Action triggers late | See Performance and testing. |
| Auto Action can't be edited | To edit an Auto Action, an account needs write access to all properties it applies to. With sub-accounts this may not be the case, for example when the Auto Action is set to trigger for All Properties. |
| Error "You don't have permission to access control2.php on this server" when you click Save | Something in your content is most likely triggering the firewall, often a script or HTML item that looks like a hacking attempt. It can also be something innocent-looking, such as a combination of numbers and words like "and" or "or" that are often used in SQL injection attacks. Add your content bit by bit until you find the item causing the problem, then reword it. |
| Auto Action isn't visible in a sub-account | Create the Auto Action in the master account, set Property to All visible in account, and make sure the master account has access to the properties. |
Examples by use case
Ready-made setups for these and many other tasks are in Auto Action examples.
| You want to | Example |
|---|---|
| Send a confirmation message to bookings from OTAs and channels | Email confirmation for channel bookings |
| Send a booking registration form (PDF) so guests can complete all guest details | Send email with Booking Registration Form |
| Confirm to the guest that a payment was received | Send an email to the guest when a payment is made |
| Send an invoice (PDF) to the guest after check-out | Send invoice after check-out |
| Confirm to the guest that their booking is cancelled | Send an email when the booking status changes to Cancelled |
| Send a payment request for all bookings | Send a request for payment for all bookings |
| Send a payment request some days after the booking | Send a request for payment XX days after booking |
| Send a payment request some days before check-in | Send a request for payment XX days before check-in |
| Stripe: authorise a security deposit on the guest's credit card before check-in | Send a request to capture a security deposit with Stripe |
| Stripe: email the guest when their payment failed | Send an email when a payment fails at Stripe |
| Stripe: ask the guest to update a credit card that expires before check-in | Send a request to update the guest's credit card |
| Send access instructions and a key code 1 day before check-in (self check-in) | Send an email with a key code for a specific unit |
| Send check-in details before check-in, only when the booking is fully paid | Send check-in details when the booking is paid |
| Send check-in details before check-in, only when the security deposit is authorised at Stripe | Send check-in details when the security deposit is authorised |