Having your operation monitored to the point where certain data values or behaviors automatically create a tracked, escalatable Incident is possible thanks to Ubidots' Events Engine. The Create Incident action opens an Incident the moment your event triggers, optionally running an Escalation Policy to make sure the right people are notified until someone responds. Learn how to set it up in a few simple steps.
1. Create a new event
To begin, head to the "Data" tab → "Events" and hover over the "+" button, located at the upper right corner of the screen, and create a conditional event, global event, or scheduled event depending on your needs.
Next, configure the event's triggers with an AND/OR logic. For additional details on how to configure these triggers, head to their corresponding guides: value based, inactivity, geofence.
2. Configure the Create Incident action
With the trigger logic configured, it's now time to set up the Create Incident action.
Click on the "+ add action" button. From the available options, select "Create Incident".
Fill in the incident details:
Incident name: The title that will be assigned to every Incident created by this event. You can use dynamic bookmarks (available via the tag icon) to include contextual information such as device name, variable value, or timestamp — for example: "High temperature alert — {{device.name}}".
Severity: The priority level of the Incident (P0–P4, from Business Critical to Request). See the Incidents article for a description of each level.
Optionally, assign an Escalation Policy to the Incident. This determines who gets notified, through which channels (Email, SMS, WhatsApp, and/or Voice Call), and what happens if nobody responds. You can either:
Select an existing Policy from the dropdown, or
Click + Create new policy to configure one inline. For a full explanation of how Escalation Policies work and how to configure them, refer to the Escalation Policies article.
If no Policy is selected, the Incident is created and tracked in the Incidents module, but no automatic notifications are sent.
In the Active trigger tab, customize the notification message that the Escalation Policy will send to recipients when the Incident is created:
Subject
Message
Use the tag icon to insert dynamic bookmarks such as device name, variable value, or timestamp.
In the Back to normal tab, configure what happens when the trigger conditions return to normal:
Auto-resolve incident: When enabled, the Incident is automatically resolved as soon as the trigger conditions return to normal.
Back to normal action: When enabled, the action also runs when the trigger conditions return to normal, sending an additional notification to the Policy recipients.
Subject and Message: Available when "Back to normal action" is enabled. Customize the content of the back-to-normal notification using the same bookmark options as above.
For more details on back-to-normal behavior, see this guide.
Click Save once you finish configuring the action, then click Next — unless you want to add more actions to the same event.
After completing the action configuration, you'll proceed to the final step: the Settings tab. There, you'll name the event and optionally give it a description.
Optionally, assign a tag to the event. This is a great tool to control what your end users see in your app — for example, you could decide that one event is visible to end users while another is not. Learn more about tags here.
Finally (unless you created a scheduled event), determine the activity window during which the event should be active. An event can have multiple active windows by clicking the "+ add window" button and configuring them accordingly. After finishing this, click Save and your event will be deployed.
Note: If this event fires and an Incident created by it is already open, no new Incident is created — the existing one's last-activity timestamp is updated instead. A new Incident is only created if the previous one has been acknowledged or resolved. |