Make: Difference between revisions

Jump to navigation Jump to search
IuriRosa (talk | contribs)
Lesley (talk | contribs)
No edit summary
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[[Category:Apps]]
[[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) APPS & INTEGRATIONS > MAKE and explains how to connect and what you can do with the connection.
  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 16: Line 16:
= Set Up =
= Set Up =
=== Beds24 ===
=== Beds24 ===
*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.
*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.
Line 71: 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.
<embedvideo service="youtube">https://youtu.be/jQAo4J6YVAI</embedvideo>


Possible values are:
Possible values are:
Line 264: Line 262:




5.  Now we will need to add another module, add the “Json” module and set it to “Create Json”
5.  Now we will need to add another module, add the “JSON” module and set it to “Create JSON”




Line 273: 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 = Json
c) Leave the “Content Type = JSON


d) On the Sample Data insert  
d) On the Sample Data insert  
Line 303: 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 Settings -> Account - > Account Access
*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 452: Line 450:




5. Now we will need to add another module, add the “Json” module and set it to “Create Json”
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 463: 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 = Json
c. Leave the “Content Type = JSON


d. On the Sample Data insert  
d. On the Sample Data insert  
Line 485: 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.2You will also need to add the correct “Google form” variables into the corresponding fields., just like the image below
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 516: 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 Json module to create a code ans set a info code in the Booking in Beds24 using the API.  
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 Json module to create the Json code and a HTTP module to send the code to Beds24 to set the info code.
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 528: Line 526:
*** Beds24 Setup.
*** Beds24 Setup.


1. Under Settings > Apps & Integrations > Integromat, set the "Send strategy=Continuously"
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,  
JSON Module,  


You will need the following Data Structure,
You will need the following Data Structure,
Line 553: Line 551:
The HTTP module
The HTTP module


You need a HTTP module after the json module and set this to “Make a Request”
You need a HTTP module after the JSON module and set this to “Make a Request”


Set the:  
Set the:  
Line 591: Line 589:
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.
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 ==
==== Step 1: Create a Data Store ====
1. Log into Make and go to '''More''' (the 2 dots) > '''Data Store'''.
1. Log into Make and go to '''More''' (the 2 dots) > '''Data Store'''.


Line 602: Line 600:
[[Media:Image3.png|view large]]
[[Media:Image3.png|view large]]


=== Configure the Data Store ===
 
''' Configure the Data Store '''
 
1. Give the data store a name (I suggest "Access Token").
1. Give the data store a name (I suggest "Access Token").
2. In the '''Data Structure''', click '''Add'''.
2. In the '''Data Structure''', click '''Add'''.
Line 644: Line 644:
[[Media:Image9.png|view large]]
[[Media:Image9.png|view large]]


== Step 2: Get Tokens from Beds24 ==
==== Step 2: Get Tokens from Beds24 ====
1. Log in to Beds24 and navigate to '''Settings > Apps & Integrations > API''' to generate a new invite code.
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].
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.
3. Click '''Try Out''' and paste your invite code.
Line 665: Line 665:
7. Click '''Save''' at the top of the screen. You now have a data store containing your token and refresh token.
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 ==
==== 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'''.
1. Create a new scenario in Make, and add the first module as '''Data Store – Search Record'''.


Line 713: Line 713:
[[Media:Image19.png|view large]]
[[Media:Image19.png|view large]]


== Step 4: Finalize the Scenario ==
==== Step 4: Finalize the Scenario ====
1. Edit the last module (Data Store) again, and map:
1. Edit the last module (Data Store) again, and map:
   * '''Access Token''' = Token from the HTTP module.
   * '''Access Token''' = Token from the HTTP module.
Line 723: Line 723:
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.
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 ==
==== 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.
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>