tutorials:using_mairlist_with_ifttt
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
tutorials:using_mairlist_with_ifttt [2016/01/11 08:58] – created tw | tutorials:using_mairlist_with_ifttt [2019/07/09 16:18] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 11: | Line 11: | ||
First of all, you need to create an account for IFTTT obviously if you don't have one already. So go to [[https:// | First of all, you need to create an account for IFTTT obviously if you don't have one already. So go to [[https:// | ||
- | To fire triggers from mAirList, we will use the so-called | + | To fire triggers from mAirList, we will use the so-called |
Maker Channels are managed on [[https:// | Maker Channels are managed on [[https:// | ||
Line 21: | Line 21: | ||
{{ : | {{ : | ||
+ | ==== Create Recipe ==== | ||
+ | Once we have connected our Maker Channel and obtained your key, you can go to //My Recipes// in the menu, and create a new recipe. For the Trigger Channel, type " | ||
+ | {{ : | ||
+ | |||
+ | As we are going to trigger the action through an HTTP call from mAirList, choose //Receive a web request// as the trigger -- this happens to be the only option at the time of this writing: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | In the next step, enter a name for the trigger. This will be later used in the URL, so use lower case characters only, and no spaces. For our example, we choose '' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | In the remaining steps, we must specify to the action to take -- in our very simple example, we will just send an email to ourself: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ==== Test the Recipe ==== | ||
+ | |||
+ | To test the recipe, go back to [[https:// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | In the topmost URL field, replace '' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Now you can click //Test It// and wait for the e-mail to arrive. | ||
+ | |||
+ | At the bottom of the page, we already see the HTTP POST URL that we will need in the final step when adding the action to mAirList: '' | ||
+ | |||
+ | ===== Set Up mAirList ===== | ||
+ | |||
+ | The final step is to make mAirList trigger the HTTP POST call when the playlist runs empty during automation. | ||
+ | |||
+ | ==== Create Script ==== | ||
+ | |||
+ | At this time, we cannot use HTTP POST calls directly in action lists, so we must create a very simple script first: | ||
+ | |||
+ | <code language=" | ||
+ | begin | ||
+ | HTTPPost(' | ||
+ | end. | ||
+ | </ | ||
+ | |||
+ | Replace ''< | ||
+ | |||
+ | ==== Set Up Action ==== | ||
+ | |||
+ | Now that we have created the script, we can go to the configuration and add it as an action to the //When playlist runs empty in automation mode// condition: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | That's all. Now when the playlist runs empty, mAirList will make a call to IFTTT. |
tutorials/using_mairlist_with_ifttt.1452502680.txt.gz · Last modified: 2019/07/09 16:19 (external edit)