In this tutorial, we are going to learn how to limit notification rate through the action flow. Note: this flow limits the events triggered from all geofences. Read More
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 post covers the basics of the Proximi.io action flows. The same content is discussed in the Zero to Hero tutorial series part 2.6. If you’ve read that, feel free to skip to the next chapter.
Action flows are optional event chains that are processed within the Web Portal instance. Action flows can include interactions with third party systems as well as with the visitor’s mobile device. Action flows are stored in our backend database, but performed within the Web Portal instance.
Our action flow editor is based on the Node-RED project which is a creation of IBM Emerging Technologies. We’ve added our own storage driver and improved the overall stability of the system, but it’s still compatible with the original Node-RED project and especially with all the community built nodes that are available.
In this example, we are sending some JSON content to a third party endpoint, when a geofence enter event is triggered. Whenever there is an enter event, we are going to pass the name of the geofence and the Visitor ID of that device that triggered it to the defined endpoint.
For this tutorial, we are going to use a free, open online service called Webhook Tester, https://webhook.site/. The service allows you to create your own custom URL with one click that you can use to easily test webhooks and other types of HTTP requests.