Make: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (21 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category: | [[Category:Marketplace]] | ||
[[Category:Automation]] | [[Category:Automation]] | ||
[[Category:Use_Cases]] | [[Category:Use_Cases]] | ||
<div class="heading">Make (formerly Integromat)</div> | <div class="heading">Make (formerly Integromat)</div> | ||
This page is about the menu {{#fas:cog}} (SETTINGS) | This page is about the menu {{#fas:cog}} (SETTINGS) MARKETPLACE > MAKE and explains how to connect and what you can do with the connection. | ||
To use this service you will need an account with [https://www.make.com/en/register?pc=beds24 Make]. | To use this service you will need an account with [https://www.make.com/en/register?pc=beds24 Make]. | ||
| Line 9: | Line 9: | ||
For Beds24 the normal channel manger fees apply. | For Beds24 the normal channel manger fees apply. | ||
= Capabilities = | |||
Within Make you can connect Beds24 to third party Apps and services. Beds24 will then send booking data to Make which will be passed on to the services you connected to | Within Make you can connect Beds24 to third party Apps and services. Beds24 will then send booking data to Make which will be passed on to the services you connected to | ||
= Limitations = | |||
= Set Up = | |||
=== Beds24 === | === Beds24 === | ||
*Set up an Auto Action | *Set up an Auto Action {{#fas:cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS which selects the bookings which will be sent to Make. Set "Trigger Action" = automatic. | ||
*Select the Auto Action which you want to use for Make. The Auto Action must be created by the Account which owns the property, actions linked from other accounts cannot be used. | *Select the Auto Action which you want to use for Make. The Auto Action must be created by the Account which owns the property, actions linked from other accounts cannot be used. | ||
*Tick the rooms for which you want to send bookings. Only bookings from rooms enabled for Make and which meet the trigger conditions in the Auto Action will be sent. | *Tick the rooms for which you want to send bookings. Only bookings from rooms enabled for Make and which meet the trigger conditions in the Auto Action will be sent. | ||
*Create an apiKey of 16 or more characters and save it. | *Create an apiKey of 16 or more characters and save it. API access must be allowed in the menu ({{#fas:cog}} (SETTINGS) ACCOUNT > ACCOUNT ACCESS). | ||
*Choose your send strategy, bookings can be sent continuously, repeatedly, once only or after each modification. | *Choose your send strategy, bookings can be sent continuously, repeatedly, once only or after each modification. | ||
*A default set of booking information is sent to Make, 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. | *A default set of booking information is sent to Make, 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. | ||
| Line 49: | Line 48: | ||
The Template Variable will be calculated and it's value sent to Make with the booking. | The Template Variable will be calculated and it's value sent to Make with the booking. | ||
<embedvideo service="youtube">https://youtu.be/rwI8_Eijeuw</embedvideo> | <embedvideo service="youtube">https://youtu.be/rwI8_Eijeuw</embedvideo> | ||
| Line 73: | Line 71: | ||
If the data fields setting is used, only the booking number, modifiedTime and the fields specified are sent to Make. | If the data fields setting is used, only the booking number, modifiedTime and the fields specified are sent to Make. | ||
Data field values must be specified one per line. | Data field values must be specified one per line. | ||
Possible values are: | Possible values are: | ||
| Line 215: | Line 211: | ||
</code> | </code> | ||
= Common Problems = | |||
'''Some bookings are not processed''' | '''Some bookings are not processed''' | ||
Make sure to set the limit value in "watch bookings" high enough to allow Make to process all the bookings you expect to be in the data. If you leave it at 1, only the first booking in each trigger will be processed. | Make sure to set the limit value in "watch bookings" high enough to allow Make to process all the bookings you expect to be in the data. If you leave it at 1, only the first booking in each trigger will be processed. | ||
| Line 224: | Line 220: | ||
[[Media:Integromat_choose_where_to_start_menu.png|view large]] | [[Media:Integromat_choose_where_to_start_menu.png|view large]] | ||
= Disconnect= | |||
Untick "Bookings" to stop sending bookings. | Untick "Bookings" to stop sending bookings. | ||
= Sample Scenarios= | |||
Make provides a range of sample scenarios at https://www.make.com/en/integrations/beds24?fromImt=1&pc=beds24. | Make provides a range of sample scenarios at https://www.make.com/en/integrations/beds24?fromImt=1&pc=beds24. | ||
| Line 267: | Line 262: | ||
5. Now we will need to add another module, add the | 5. Now we will need to add another module, add the “JSON” module and set it to “Create JSON” | ||
| Line 276: | Line 271: | ||
b) “Name the data structure” and click on “Generator” | b) “Name the data structure” and click on “Generator” | ||
c) Leave the “Content Type = | c) Leave the “Content Type = JSON | ||
d) On the Sample Data insert | d) On the Sample Data insert | ||
| Line 306: | Line 301: | ||
[[Media:integromat_subaccount4.png|view large]] | [[Media:integromat_subaccount4.png|view large]] | ||
*You need to set the API key you have set under | *You need to set the API key you have set under {{#fas:cog}} (SETTINGS) ACCOUNT > ACCOUNT ACCESS | ||
*Click on “Add Items” under Create Account in Make, here you will need to add the variables into the correct fields. | *Click on “Add Items” under Create Account in Make, here you will need to add the variables into the correct fields. | ||
| Line 387: | Line 382: | ||
[[Image:push7.jpg|650px|link=]] | [[Image:push7.jpg|650px|link=]] | ||
[[Media:push7.jpg|view large]] | [[Media:push7.jpg|view large]] | ||
</div> | </div> | ||
</div> | </div> | ||
| Line 593: | Line 450: | ||
5. Now we will need to add another module, add the | 5. Now we will need to add another module, add the “JSON” module and set it to “Create JSON” | ||
[[Image:Guestinfofromdoc5.png|650px|link=]] | [[Image:Guestinfofromdoc5.png|650px|link=]] | ||
| Line 604: | Line 461: | ||
b. “Name the data structure” and click on “Generator” | b. “Name the data structure” and click on “Generator” | ||
c. Leave the “Content Type = | c. Leave the “Content Type = JSON | ||
d. On the Sample Data insert | d. On the Sample Data insert | ||
| Line 626: | Line 483: | ||
6.1. Click on “Save”, you should now see the original “window” with your data structure and it should have a “Authentication” box where you need to insert the API key | 6.1. Click on “Save”, you should now see the original “window” with your data structure and it should have a “Authentication” box where you need to insert the API key | ||
6. | 6.2. You will also need to add the correct “Google form” variables into the corresponding fields., just like the image below | ||
[[Image:Guestinfofromdoc6.png|650px|link=]] | [[Image:Guestinfofromdoc6.png|650px|link=]] | ||
| Line 657: | Line 514: | ||
Due to a combination of some settings and or specific modules in Make sometimes Make can miss out on bookings sent to Make. | Due to a combination of some settings and or specific modules in Make sometimes Make can miss out on bookings sent to Make. | ||
If this happens on a frequent basis we recommend that you setup Beds24 to continuously send the bookings to Make, once the bookings is correctly picked up by Make you can setup a | If this happens on a frequent basis we recommend that you setup Beds24 to continuously send the bookings to Make, once the bookings is correctly picked up by Make you can setup a JSON module to create a code ans set a info code in the Booking in Beds24 using the API. | ||
This way once a booking is correctly sent it will contain the Info code and based on this info code you can filter out this booking the next time it is sent to Make stopping the bookings from going thru any other modules in Make. | This way once a booking is correctly sent it will contain the Info code and based on this info code you can filter out this booking the next time it is sent to Make stopping the bookings from going thru any other modules in Make. | ||
Each customer has its own Make module setup and so it is hard to create a scenario valid for everyone, however the only thing we need to setup is 2 modules a | Each customer has its own Make module setup and so it is hard to create a scenario valid for everyone, however the only thing we need to setup is 2 modules a JSON module to create the JSON code and a HTTP module to send the code to Beds24 to set the info code. | ||
Have a look at the following video to understand how the sequence will work, | Have a look at the following video to understand how the sequence will work, | ||
| Line 669: | Line 526: | ||
*** Beds24 Setup. | *** Beds24 Setup. | ||
1. Under | 1. Under {{#fas:cog}} (SETTINGS) MARKETPLACE > MAKE, set the "Send strategy=Continuously" | ||
In the Data fields set all the necessary fields that you need to pass from Beds24 to Make, it is required that you set a "template" field (template1), we are using this to pass the Info code to Make. | In the Data fields set all the necessary fields that you need to pass from Beds24 to Make, it is required that you set a "template" field (template1), we are using this to pass the Info code to Make. | ||
Make Setup. | Make Setup. | ||
JSON Module, | |||
You will need the following Data Structure, | You will need the following Data Structure, | ||
| Line 694: | Line 551: | ||
The HTTP module | The HTTP module | ||
You need a HTTP module after the | You need a HTTP module after the JSON module and set this to “Make a Request” | ||
Set the: | Set the: | ||
| Line 717: | Line 574: | ||
1. Set a "Text Operator" filter "Not Equal To" | 1. Set a "Text Operator" filter "Not Equal To" | ||
</div> | |||
</div> | |||
<div class="mw-collapsible mw-collapsed"> | |||
<div class="headline-collapse" > | |||
=== Connect to API V2 === | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
'''Connecting Make to Beds24 API V2''' | |||
Before using API V2 with Make, we need to set up a data store to store the refresh token and the access token. We will also need to create a scenario that triggers every 24 hours to obtain a new token using the refresh token. Once this is set up, we can configure any scenario in Make using the Beds24 API V2, as we will always have an up-to-date token. | |||
==== Step 1: Create a Data Store ==== | |||
1. Log into Make and go to '''More''' (the 2 dots) > '''Data Store'''. | |||
[[Image:Image1.png|700px|link=]] | |||
[[Media:Image1.png|view large]] | |||
2. Click the '''Add Data Store''' button in the top right corner. | |||
[[Image:Image3.png|700px|link=]] | |||
[[Media:Image3.png|view large]] | |||
''' Configure the Data Store ''' | |||
1. Give the data store a name (I suggest "Access Token"). | |||
2. In the '''Data Structure''', click '''Add'''. | |||
[[Image:Image4.png|700px|link=]] | |||
[[Media:Image4.png|view large]] | |||
* Click '''Add Item''' and set: | |||
* '''Name''' = “Access Token” | |||
* '''Type''' = Text | |||
* '''Required''' = No | |||
* '''Multi-line''' = No | |||
[[Image:Image5.png|700px|link=]] | |||
[[Media:Image5.png|view large]] | |||
3. Click '''Add New Item''' and set: | |||
[[Image:Image6.png|700px|link=]] | |||
[[Media:Image6.png|view large]] | |||
* '''Name''' = "Refresh Token" | |||
* '''Type''' = Text | |||
* '''Required''' = No | |||
* '''Multi-line''' = No | |||
* '''Strict''' = No | |||
4. Click '''Save''' to save the data structure and the data store. | |||
5. Now click '''Browse''' to find the data store you just created. | |||
[[Image:Image7.png|700px|link=]] | |||
[[Media:Image7.png|view large]] | |||
6. Click '''Add''' at the top of the screen. | |||
[[Image:Image8.png|700px|link=]] | |||
[[Media:Image8.png|view large]] | |||
7. You will need to add a key. Click the icon and enter a random number; you will need this number later for your scenario. | |||
[[Image:Image9.png|700px|link=]] | |||
[[Media:Image9.png|view large]] | |||
==== Step 2: Get Tokens from Beds24 ==== | |||
1. Log in to Beds24 and navigate to '''Settings > MARKETPLACE > API''' to generate a new invite code. | |||
2. After you have the invite code, visit [https://api.beds24.com/v2/#/Authentication/get_authentication_setup Beds24 API Authentication Setup]. | |||
3. Click '''Try Out''' and paste your invite code. | |||
[[Image:Image10.png|700px|link=]] | |||
[[Media:Image10.png|view large]] | |||
4. Click '''Execute''' to retrieve your token and refresh token. | |||
[[Image:Image11.png|700px|link=]] | |||
[[Media:Image11.png|view large]] | |||
5. Copy the access token and paste it into the "Access Token" field in the data store. | |||
6. Copy the refresh token and paste it into the "Refresh Token" field in the data store. | |||
[[Image:Image12.png|700px|link=]] | |||
[[Media:Image12.png|view large]] | |||
7. Click '''Save''' at the top of the screen. You now have a data store containing your token and refresh token. | |||
==== Step 3: Create a Scenario to Update the Token Every 24 Hours ==== | |||
1. Create a new scenario in Make, and add the first module as '''Data Store – Search Record'''. | |||
[[Image:Image13.png|700px|link=]] | |||
[[Media:Image13.png|view large]] | |||
* Select '''Browse''' and choose the data store you created. | |||
* In the filter, choose the '''Access Token'''. | |||
* Set '''Basic Operation''' = Exist (this is important to check if the token exists). | |||
[[Image:Image14.png|700px|link=]] | |||
[[Media:Image14.png|view large]] | |||
2. Click '''OK''' and add the second module. | |||
3. Add an '''HTTP module – Make a Request''' to request a new token every 24 hours: | |||
* Set '''Evaluate all states as errors''' (except for 2xx and 3xx) = No. | |||
* '''URL''' = https://api.beds24.com/v2/authentication/token. | |||
* '''Method''' = GET. | |||
* In the headers, add two items: | |||
* '''Item 1''': Name = '''refreshToken''', Value = map the refresh token from the first module (Data Store module). | |||
[[Image:Image16.png|700px|link=]] | |||
[[Media:Image16.png|view large]] | |||
* '''Item 2''': Name = '''accept''', Value = '''application/json'''. | |||
4. Save the module. | |||
5. Add another module to update the token: '''Data Store – Add / Replace Record'''. | |||
* Select the data store you created. | |||
* '''Key''' = the random number you set earlier. | |||
* '''Overwrite an existing record''' = Yes. | |||
* '''Parse response''' = Yes (this is crucial). | |||
6. You will need to run the HTTP module once before proceeding. Save the data store module as is for now. | |||
[[Image:Image17.png|700px|link=]] | |||
[[Media:Image17.png|view large]] | |||
7. Copy your refresh token again and paste it into the "Refresh Token" field. | |||
[[Image:Image18.png|700px|link=]] | |||
[[Media:Image18.png|view large]] | |||
8. Click '''OK''' to run the module and update your token. | |||
[[Image:Image19.png|700px|link=]] | |||
[[Media:Image19.png|view large]] | |||
==== Step 4: Finalize the Scenario ==== | |||
1. Edit the last module (Data Store) again, and map: | |||
* '''Access Token''' = Token from the HTTP module. | |||
* '''Refresh Token''' = Refresh token from the Data Store module. | |||
[[Image:Image20.png|700px|link=]] | |||
[[Media:Image20.png|view large]] | |||
2. Save the module and set it to trigger every 24 hours. This will make an API call every day to get a new token. | |||
==== Step 5: Using the Token in API Calls ==== | |||
To make API calls to Beds24, first set the '''Data Store module – Get a Record'''. Insert your key (the number you set under Key). When you set up an HTTP module to make an API call, use the token from the data store, which will always be up to date. | |||
</div> | </div> | ||
</div> | </div> | ||