Our Zapier integration currently supports only pressed or not pressed triggers. We'll be adding short / long press in the future, but in the meanwhile you can differentiate between the two as described below.
Tip 1: Zapier now allows you to chain several actions in one Zap, and also use conditional filters between the actions.
Tip 2: The same idea may work with IFTTT's Maker Channel.
METHOD 1 - SIMPLE - Sending two different webhooks from bt.tn server to Zapier
This method involves creating two Zaps. bttn is set to use short / long press demo action.
Start to create Zap #1
1) Go to Zapier and create a new Zap.
2) Select "Webhooks by Zapier" as trigger
3) Select "Catch Hook" and click next until you get an URL for your Zapier webhook #1.
4) Copy the Zapier webhook URL to your clipboard.
Start to create bttn action:
5) Open my.bt.tn in new browser tab
6) Configure a new action for your bttn, selecting "SHORT / LONG PRESS (DEMO)" under 3rd party services
7) Paste your Zapier webhook #1 URL to short press URL
8) Manually enter text "?event=short" (without the quotes) to the end of the url
Start to create Zap #2:
9) Open another browser tab for Zapier and create yet another Zap
10) Select "Webhooks by Zapier" as trigger
11) Select "Catch Hook" and click next until you get an URL for your Zapier webhook #2.
12) Copy the Zapier webhook #2 URL to your clipboard.
Finalize bttn action:
13) Go back to my.bt.tn browser tab and paste the second url to long press URL
14) Manually enter text "?event=long" (without the quotes) to the end of the url
15) Proceed to save your bttn action.
16) Make both a short press and a long press (Zapier expects to see these).
Finalize Zaps 1 & 2
17) Go back to your Zap #1 and finalize it by specifying your target action, e.g. an email.
18) Go back to your Zap #2 and finalize it by specifying your target action, e.g. an SMS.
That's it ! Now you should have two Zaps that are triggered by separate HTTP GET requests sent by short / long press.
-----------------------
METHOD 2 - ADVANCED - Using Zapier to filter the press type
This method involves creating 3 Zaps. bttn can be configured to simply use Zapier action.
Zap 1 = bttn triggers 2 Zapier webhooks, making POST requests.
Zap 2 = Zapier webhook triggers action X, and the Zap contains a filter for advancing only if it's a long press.
Zap 3 = Zapier webhook triggers action Y, and the Zap contains a filter for advancing only if it's a short press.
See pictures below.
Picture 1: Your finished setup will look something like this.
Picture 2: The POST data for the bttn triggered Zapier webhooks.
Picture 3: Using Zapier filter: short press event description = "pressed" and long press event description = "pressed-long".
