What are Triggers?
CloudPlugs IoT Trigges allow you to define one or multiple actions to be executed based on rules relative to device status changes, and data published on the platform. Currently supported actions are:
- Near real time e-mail notifications.
- Near real time SMS notifications.
- HTTP requests.
- Publish data.
- Create a JIRA trouble ticket.
The actions are executed based on rules programmed by the user. Five (5) types of rules can be programmed:
- Thresholds, which allow you to set Thresholds and program actions when the thresholds are crossed.
- Location, which allows you to set geo-fencing boundaries and program actions based on device location relative to the geo-fence.
- State, used to program actions based on device state changes, or when a device remains in its current state.
- Bit mask used to program actions based on the value of individual bits of the data received by the platform.
- Any Data, used to program actions when any type of data is received by the platform.
Triggers can be defined for Prototypes, Production Templates, Production Things and Controllers. Production Templates inherit their Prototype triggers, and Production Things inherit their Production Template triggers.
- The first time a trigger is created for a Prototype, Production Template, Production Thing, or Controller device, the device must also be saved for the trigger to become enabled.
- If an existing trigger is edited and saved, the corresponding device does not have to be saved for the trigger to become enabled.
To learn how to program triggers, please refer to the Trigger Programming Guide.