PushingBox is a cloud service that sends notifications based on API calls — you can trigger the service by HTTP request (GET/POST) or email. PushingBox is called from almost anything, e.g., Arduino, Spark Core, IFTTT, email, SmartThings, an HTTP request or your own script. Dozens of services, such as emails, Tweets, SmartWatch notifications, Push Notifications (iOS, Android, WindowsPhone), Windows8 Notifications and MacOS Notifications can be utilized.
In a previous blog post, Revolution11 introduced iBeacons, Apple’s protocol that allows mobile devices (iOS and Android) to pick up signals from small sensors using the Bluetooth Low Energy (BLE) protocol. The uses for iBeacons are endless, and as our consumption of “stuff” from mobile devices increases, sensors such as iBeacons will deliver rich contextual content from everyday objects.
In this example, we combine iBeacons with PushingBox API and Pushbullet to send notifications to iOS devices and Chrome browser with a FileMaker solution.
Set-Up:
1. Go to https://www.pushingbox.com/ and sign up for an account. Notifications are created from an API call to the services supported by PushingBox. Next, configure the service you are sending the notification from. You can do it at the My Services page.
2. Add a service:
3. Select the Pushbullet service:
The Pushbullet Service dialog box will prompt you to name the service and enter the access token used in the API call.
4. Download Pushbullet at this point by clicking on the link (1)
5. Signup for a Pushbullet account and Create an Access Token (2). You can use a Google account to sign into the PushingBox and Pushbullet accounts making it simple and quick.
a. Enter the access token back in the Pushbullet service.
6. Create a “scenario” and add an action to which the service will use and eventually write the text to send. The action is essentially the customized information you will use in your scenario.
a. Go to “My Scenarios” and give the service a name of your choice and click “Add”
b. This is step is where you will get the DeviceID used in the API call. Select “Manage”
7. Select “Add an Action” and note your DeviceID:
Pushbullet or any other scenario you’ve set up will be available to add an action too.
8. Select “Add an action with this service”
From here you can create the message you want to send or use variables if you want to send some customized information with your scenario.
Here we are creating variables for use in a FileMaker solution, in this example we create variables:
$MessageTitle$
$RSE_Message$
Be on the lookout for our next blog post where we will create the FileMaker solution and integrate it with iBeacons, PushingBox, and Pushbullet Web service. Revolution11 is continually seeking innovative solutions for our clients.
Download a PDF here: PushingBox API