The “Advanced Action Flows” tutorial series

 

The action flow editor is one of the most awesome features that our proximity portal offers. Its intuitive click-and-drag UI to create flows eases up the process – so that with only basic JavaScript knowledge, you can set up complex reactions to location-based events.

In this extensive tutorial series, we hope to provide some practical examples and to walk you through the nodes’ usage in our action flow editor.

For more in-depth guides, please refer to the official Node-RED documentations.

To integrate to your own app

Now that you are ready with your setup, We do warmly recommend testing it out with our Management Applications, to ensure that everything is working well regarding your setup. Once you are happy with the result, go ahead and integrate our platform to your application!

For each framework we have both an SDK file, and a base app that can be used as the starting point for app development.

Note: You’ll find your auth token on the portal under “Manage Application”. There are two seperate token types and the default token to use is the Mobile token, but there are some rare cases where using the other token is also applicapble. Here is a rundown of which token to use:

Master token and Mobile Token

 

Master token

Master token is the key to all of your account’s features. The Master token will grant access to all objects and all operations (CREATE, READ, UPDATE and DELETE). This is especially meant to be used when doing REST API calls with our endpoints. We strongly advise you to use this token with care and only use it in the mobile app when it is detrimental to the functionalities of the app.

There can only be one master token and this token cannot be deleted or changed. If you believe the master token has ended up in the wrong hands, please inform us immediately and we will change it for you.

 

Mobile token

On the mobile side we have made some precautionary security measures to prevent your master token ending up in the wrong hands. With the mobile token you get access to all objects with limited operations. If this token ends up to the wrong people, they don’t have the ability to delete and create any crucial elements of your setup.

With the Mobile token you READ for core objects like places, geofences etc. and READ & WRITE for position updates and event. This token is recommended to be used within mobile applications when using our SDK.This applies when you are integrating our SDK into your own application, when you are asked to provide our auth_token, you should use the Mobile token for this matter. More information can he found here: (https://proximi.io/part-8-integrating-app/)

NOTICE! There are exceptions to using the Mobile token in apps. In use cases where the app requires functionalities like CREATING and DELETING objects within the app, you would need to use the Master token.

You can create multiple Mobile tokens to with different setups and they can be changed and deleted, if needed.

Important: Even though this flow works in theory, in practice this type of usage is currently blocked by most email providers. We cannot help with issues relating to using this flow.
This tutorial will guide you through the process on how to define a action flow to send email to an user when there is an enter event to a defined geofence. This could come in handy when you want to be notified whenever an valuable customer enters your shop, restaurant or any other social gathering. We are going to have two geofences one defined at the entrance of the shop and one at the exit door. In this example, the geofences are called: Entrance Geofence and Exit Geofence.  (more…)