Difference between revisions of "Make"
Markkinchin (talk | contribs) |
Markkinchin (talk | contribs) |
||
| Line 55: | Line 55: | ||
unitName | unitName | ||
status | status | ||
| − | checkIn | + | checkIn |
| − | checkOut | + | checkOut |
| − | numAdult | + | numAdult |
| − | numChild | + | numChild |
| − | guestTitle | + | guestTitle |
| − | guestFirstName | + | guestFirstName |
| − | guestLastName | + | guestLastName |
| − | guestComments | + | guestComments |
| − | guestArrivalTime | + | guestArrivalTime |
| − | guestEmail | + | guestEmail |
| − | guestPhone | + | guestPhone |
| − | guestMobile | + | guestMobile |
| − | guestCompany | + | guestCompany |
| − | guestAddress | + | guestAddress |
| − | guestCity | + | guestCity |
| − | guestState | + | guestState |
| − | guestPostCode | + | guestPostCode |
| − | guestCountry | + | guestCountry |
| − | guestCountry2 | + | guestCountry2 |
| − | lang | + | lang |
| − | originalBooking | + | originalBooking |
| − | originalOTA | + | originalOTA |
| − | originalReferer | + | originalReferer |
| − | referer | + | referer |
| − | notes | + | notes |
| − | reference | + | reference |
| − | custom1 | + | custom1 |
| − | custom2 | + | custom2 |
| − | custom3 | + | custom3 |
| − | custom4 | + | custom4 |
| − | custom5 | + | custom5 |
| − | custom6 | + | custom6 |
| − | custom7 | + | custom7 |
| − | custom8 | + | custom8 |
| − | custom9 | + | custom9 |
| − | custom10 | + | custom10 |
| − | offerId | + | offerId |
| − | voucher | + | voucher |
| − | bookingTime | + | bookingTime |
| − | modifiedTime | + | modifiedTime |
| − | invoice | + | invoice |
| − | invoiceCharges | + | invoiceCharges |
| − | invoicePayments | + | invoicePayments |
| − | totalCharges | + | totalCharges |
| − | totalPayments | + | totalPayments |
| − | totalBalance | + | totalBalance |
| − | price | + | price |
| − | tax | + | tax |
| − | deposit | + | deposit |
| − | commission | + | commission |
| − | rateDescription | + | rateDescription |
| − | template1 | + | template1 |
| − | template2 | + | template2 |
| − | template3 | + | template3 |
| − | template4 | + | template4 |
| − | template5 | + | template5 |
| − | template6 | + | template6 |
| − | template7 | + | template7 |
| − | template8 | + | template8 |
== Common Problems == | == Common Problems == | ||
Revision as of 15:10, 3 February 2019
This page is about the menu SETTINGS->APPS & INTEGRATIONS->INTEGROMAT
+++++This function is in beta testing++++
To use this service you will need an account with Integromat.
For Beds24 the normal channel manger fees apply.
Contents
1 Capabilities
Within Integromat you can connect Beds24 to third party Apps and services. Beds24 will then send booking data to Integromat which will be passed on to the services you connected to
2 Limitations
3 Set Up
3.1 Beds24
- Set up an Auto Action (SETTINGS-GUEST MANAGEMENT-AUTO ACTIONS) which selects the bookings which will be sent to Integromat. Set "Trigger Action" = automatic.
- Select the Auto Action which you want to use for Integromat.
- Tick the rooms for which you want to send bookings. Only bookings from rooms enabled for Integromat and which meet the trigger conditions in the Auto Action will be sent.
- Create an apiKey of 16 or more characters and save it.
- Choose your send strategy, bookings can be sent repeatedly, once only or after each modification.
- A default set of booking information is sent to Integromat, this can be customized by specifying the fields you want to send, one per line at the setting "Data fields". See below for a set of all fields.
3.2 Integromat
- Create an Integromat account at Integromat.
- Search for the Beds24 App.
- Connect the Beds24 App to your scenario and enter the apiKey you created and the Beds24 Property Id.
- The advanced section of the Integromat connection form has eight template fields where you can enter Beds24 Template Variables, these will be calculated and returned with each booking. The matching "template" data field must be specified at the data fields setting.
- Select the trigger "watch bookings" and map the data into your scenario as you require.
4 How it works
In Integromat you create a scenario which automates tasks for you. A scenario is comprised of a series of modules that indicate how data should be transferred and transformed between Beds24 and other apps/services.
Bookings are sent from Beds24 to Integromat when the room is enabled and the booking meets the trigger condition in the selected auto action. Bookings which were sent will appear in Integromat via the "watch bookings" trigger.
These bookings will then be automatically transferred from Integromat to the apps/services in your Integromat scenarios.
5 Data Fields
If the data fields setting is left empty, a default set of information will be sent about each booking.
If the data fields setting is used, only the booking number and the fields specified are sent to Integromat. Data field values must be specified one per line.
Possible values are:
groupId roomId roomName unitId unitName status checkIn checkOut numAdult numChild guestTitle guestFirstName guestLastName guestComments guestArrivalTime guestEmail guestPhone guestMobile guestCompany guestAddress guestCity guestState guestPostCode guestCountry guestCountry2 lang originalBooking originalOTA originalReferer referer notes reference custom1 custom2 custom3 custom4 custom5 custom6 custom7 custom8 custom9 custom10 offerId voucher bookingTime modifiedTime invoice invoiceCharges invoicePayments totalCharges totalPayments totalBalance price tax deposit commission rateDescription template1 template2 template3 template4 template5 template6 template7 template8
6 Common Problems
7 Disconnect
Untick "Bookings" to stop sending bookings.
